System, method, and computer program product for determining an event in a distributed data system

ABSTRACT

A method for preventing duplicate processing of a payment transaction includes: generating a first data structure with a first predetermined time interval and generating a second data structure with a second predetermined time interval. A first overlap region and second overlap region of the first and second predetermined time interval are defined by a same time interval. The method includes receiving first transaction data associated with a first payment transaction, receiving second transaction data associated with a second payment transaction, and determining based on a first transaction ID and a second transaction ID, that the second payment transaction is a duplicate of the first payment transaction. A computer program product and system for preventing duplicate processing of a payment transaction are also disclosed.

BACKGROUND OF THE INVENTION Field of the Invention

The invention relates to a system, method, and computer program productfor determining an event in a distributed data system and, in oneparticular embodiment, to a system, method, and computer program productfor preventing duplicate processing of a payment transaction.

Description of Related Art

A distributed database system may include a database in which storagedevices are not all attached to a common processor. The database may bestored in multiple computers, located in the same physical location, ormay be dispersed over a network of interconnected computers. Unlike aparallel systems, in which processors may be part of a single databasesystem, a distributed database system may consist of sites that share nophysical components. In some instances, a distributed database mayreside on organized network servers or decentralized independentcomputers on the Internet, on corporate intranets or extranets, or onother organization networks.

An event may be an action or occurrence recognized by a computer system,which may originate asynchronously from an external environment, thatmay be handled by the computer system. Events may be generated ortriggered by the computer system, by a user of the computer system, orin other ways. In some instances, events may be handled synchronouslywith a program flow by a computer system. For example, the computersystem may have one or more dedicated places where events are handled(e.g., one or more dedicated event loops). In some instances, events mayinclude requests from a computer system, for example, a request from aprocessor. Additionally, or alternatively, the computer system may storean event (e.g., a request) in a distributed database system.

Whether from a fraudulent source or a glitch in a computer system, aduplicate request may be submitted to a processor. A duplicate requestis defined as a request identical to a previously submitted request tothe computer system that was previously processed correctly tocompletion. A computer system receiving a duplicate request mustdetermine whether a previously-submitted request associated with theduplicate request has been processed in order to determine that therequest is a duplicate request. In many end-use cases, not identifying arequest as a duplicate request and processing the duplicate request isundesirable and can have negative consequences to the computer system(because the previously-submitted request associated with the duplicaterequest has already been processed).

Several non-limiting examples of computer-implemented systems that wouldexperience negative consequences from re-processing of duplicaterequests include: processing of payment transactions, processing oftokenized transactions, processing of a temporary password, orprocessing of a temporary offer. However, other computer systems forprocessing data, including time-sensitive data, would also experiencenegative consequences from re-processing of a duplicate request.

To determine whether a request is a duplicate request, certain existingsystems utilize a global data structure, such as a global database thatincludes all data in a single database, and determines whether theprocessing request is a duplicate processing request using a uniqueglobal index associated with each data entry stored therein. This methodis inefficient because it can require querying the entire globaldatabase in search of an identical request that has already beenprocessed. In addition, with ever increasing data volumes, it isoftentimes impractical to use a single global database because it is notpossible to maintain such large datasets or sufficient hardware is costprohibitive.

Other existing systems used to determine whether a request is aduplicate request and that do not use a global database may segment thedata into separate, non-overlapping data structures based on aparameter, such as a time parameter. Such systems, however, run a riskof not identifying a request as a duplicate (leading to duplicateprocessing of identical requests) for data at the edges of the segmenteddata structure. Data at the edges of each separate data structure isparticularly vulnerable to being misallocated, should the computingsystem malfunction for any period of time and store the data to adifferent data structure.

For example, a data entry expected to be near the end in a firstsegmented data structure based on a timestamp may instead be included asone of the early entries in the second segmented data structureincluding data immediately subsequent to data in the first segmenteddata structure. This may be for any number of reasons, such as thesystem malfunctioning at the time associated with data stored at the endof the first segmented data structure, causing the data entry to bestored once the system is functioning correctly again. Thus, existingsystems including separate, non-overlapping data structures areespecially at risk of not identifying a request as a duplicate requestand, therefore, processing the duplicate request for data stored at theedges of each segmented data structure.

SUMMARY OF THE INVENTION

Accordingly, provided is an improved method, computer program product,and system for preventing duplicate processing of a payment transaction.

According to a non-limiting embodiment or aspect, provided is a methodfor preventing duplicate processing of a payment transaction including:generating, with at least one processor, a plurality of data structures,where generating the plurality of data structures includes: generating afirst data structure associated with a first unique identifier, wherethe first data structure is associated with a first predetermined timeinterval, where the first predetermined time interval is defined by afirst start time and a first end time, where the first data structurestores transaction data associated with a payment transaction that isinitiated within the first predetermined time interval; and generating asecond data structure associated with a second unique identifier, wherethe second data structure is associated with a second predetermined timeinterval, where the second predetermined time interval is defined by asecond start time and a second end time, where the second data structurestores transaction data associated with a payment transaction that isinitiated within the second predetermined time interval, where thesecond end time is after the first start time and before the first endtime, and the second end time is after the first end time, where thefirst data structure includes a first overlap region and the second datastructure includes a second overlap region, where the first overlapregion and the second overlap region are defined by an overlap timeinterval, where the overlap time interval is defined between the secondstart time and the first end time; receiving, with at least oneprocessor, first transaction data associated with a first paymenttransaction, where the first transaction data includes a first timestampassociated with initiation of the first payment transaction and a firsttransaction ID; determining, with at least one processor and based onthe first timestamp, that the first payment transaction falls within theoverlap time interval; upon determining that the first paymenttransaction falls within the overlap time interval storing, with atleast one processor, the first transaction data to the first datastructure and the second data structure; receiving, with at least oneprocessor, second transaction data associated with a second paymenttransaction, where the second transaction data includes a secondtimestamp associated with initiation of the second payment transactionand a second transaction ID; determining, with at least one processorand based on the second timestamp, that the second payment transactionfalls within the overlap time interval; and upon determining that thesecond payment transaction falls within the overlap time interval,determining, with at least one processor and based on the firsttransaction ID and the second transaction ID, that the second paymenttransaction is a duplicate of the first payment transaction.

In one non-limiting embodiment or aspect, the method may furtherinclude: upon determining that the second payment transaction is aduplicate of the first payment transaction, terminating, with at leastone processor, processing of the second payment transaction. The methodmay further include: upon determining that the second paymenttransaction is a duplicate of the first payment transaction, generatingand communicating, with at least one processor, a duplicate transactionresponse, where the duplicate transaction response includes dataassociated with identifying the second payment transaction as identicalto the first payment transaction. The method may further include: upondetermining that the second payment transaction is a duplicate of thefirst payment transaction, generating and communicating, with at leastone processor, a duplicate transaction response, where the duplicatetransaction response is identical to a response message communicated inconnection with processing of the first payment transaction.

In one non-limiting embodiment or aspect, the first data structure andthe second data structure may be stored on separate servers. Determiningthat the second payment transaction is a duplicate of the first paymenttransaction may include receiving a return value in response to arequest to store the second transaction data. The method may furtherinclude: upon determining that the second payment transaction is aduplicate of the first payment transaction, initiating a fraudulenttransaction submission protocol. The first predetermined time intervaland/or the second predetermined time interval may include at least onemonth. The overlap time interval may include from one minute to one day.The first transaction data and/or second transaction data may bereceived in the form of a transaction processing request message.

According to a non-limiting embodiment or aspect, provided is a computerprogram product for preventing duplicate processing of a paymenttransaction including at least one non-transitory computer-readablemedium including program instructions that, when executed by at leastone computer including at least one processor, causes the at least onecomputer to: generate a plurality of data structures, where generatingthe plurality of data structures includes: generating a first datastructure associated with a first unique identifier, where the firstdata structure is associated with a first predetermined time interval,where the first predetermined time interval is defined by a first starttime and a first end time, where the first data structure storestransaction data associated with a payment transaction that is initiatedwithin the first predetermined time interval; and generating a seconddata structure associated with a second unique identifier, where thesecond data structure is associated with a second predetermined timeinterval, where the second predetermined time interval is defined by asecond start time and a second end time, where the second data structurestores transaction data associated with a payment transaction that isinitiated within the second predetermined time interval, where thesecond end time is after the first start time and before the first endtime, and the second end time is after the first end time, where thefirst data structure includes a first overlap region and the second datastructure includes a second overlap region, where the first overlapregion and the second overlap region are defined by an overlap timeinterval, where the overlap time interval is defined between the secondstart time and the first end time; receive first transaction dataassociated with a first payment transaction, where the first transactiondata includes a first timestamp associated with initiation of the firstpayment transaction and a first transaction ID; determine based on thefirst timestamp, that the first payment transaction falls within theoverlap time interval; upon determining that the first paymenttransaction falls within the overlap time interval store the firsttransaction data to the first data structure and the second datastructure; receive second transaction data associated with a secondpayment transaction, where the second transaction data includes a secondtimestamp associated with initiation of the second payment transactionand a second transaction ID; determine based on the second timestamp,that the second payment transaction falls within the overlap timeinterval; and upon determining that the second payment transaction fallswithin the overlap time interval, determine based on the firsttransaction ID and the second transaction ID, that the second paymenttransaction is a duplicate of the first payment transaction.

In one non-limiting embodiment or aspect, the first data structure andthe second data structure may be stored on separate servers.

According to a non-limiting embodiment or aspect, provided is a systemfor preventing duplicate processing of a payment transaction includingat least one server computer including at least one processor, the atleast one server computer programmed and/or configured to: generate aplurality of data structures, where generating the plurality of datastructures includes: generating a first data structure associated with afirst unique identifier, where the first data structure is associatedwith a first predetermined time interval, where the first predeterminedtime interval is defined by a first start time and a first end time,where the first data structure stores transaction data associated with apayment transaction that is initiated within the first predeterminedtime interval; and generating a second data structure associated with asecond unique identifier, where the second data structure is associatedwith a second predetermined time interval, where the secondpredetermined time interval is defined by a second start time and asecond end time, where the second data structure stores transaction dataassociated with a payment transaction that is initiated within thesecond predetermined time interval, where the second end time is afterthe first start time and before the first end time, and the second endtime is after the first end time, where the first data structureincludes a first overlap region and the second data structure includes asecond overlap region, where the first overlap region and the secondoverlap region are defined by an overlap time interval, where theoverlap time interval is defined between the second start time and thefirst end time; receive first transaction data associated with a firstpayment transaction, where the first transaction data includes a firsttimestamp associated with initiation of the first payment transactionand a first transaction ID; determine based on the first timestamp, thatthe first payment transaction falls within the overlap time interval;upon determining that the first payment transaction falls within theoverlap time interval, store the first transaction data to the firstdata structure and the second data structure; receive second transactiondata associated with a second payment transaction, where the secondtransaction data includes a second timestamp associated with initiationof the second payment transaction and a second transaction ID; determinebased on the second timestamp, that the second payment transaction fallswithin the overlap time interval; and upon determining that the secondpayment transaction falls within the overlap time interval, determinebased on the first transaction ID and the second transaction ID, thatthe second payment transaction is a duplicate of the first paymenttransaction.

In one non-limiting embodiment or aspect, the at least one servercomputer may be programmed and/or configured to: upon determining thatthe second payment transaction is a duplicate of the first paymenttransaction, terminate processing of the second payment transaction. Theat least one server computer may be programmed and/or configured to:upon determining that the second payment transaction is a duplicate ofthe first payment transaction, generate and communicate a duplicatetransaction response, where the duplicate transaction response includesdata associated with identifying the second payment transaction asidentical to the first payment transaction. The at least one servercomputer may be programmed and/or configured to: upon determining thatthe second payment transaction is a duplicate of the first paymenttransaction, generate and communicate a duplicate transaction response,where the duplicate transaction response is identical to a responsemessage communicated in connection with processing of the first paymenttransaction.

In one non-limiting embodiment or aspect, the first data structure andthe second data structure may be stored on separate servers. Determiningthat the second payment transaction is a duplicate of the first paymenttransaction may include receiving a return value in response to arequest to store the second transaction data. The at least one servercomputer may be programmed and/or configured to: upon determining thatthe second payment transaction is a duplicate of the first paymenttransaction, initiate a fraudulent transaction submission protocol.

Further embodiments or aspects are set forth in the following numberedclauses:

Clause 1: A method for preventing duplicate processing of a paymenttransaction comprising: generating, with at least one processor, aplurality of data structures, wherein generating the plurality of datastructures comprises: generating a first data structure associated witha first unique identifier, wherein the first data structure isassociated with a first predetermined time interval, wherein the firstpredetermined time interval is defined by a first start time and a firstend time, wherein the first data structure stores transaction dataassociated with a payment transaction that is initiated within the firstpredetermined time interval; and generating a second data structureassociated with a second unique identifier, wherein the second datastructure is associated with a second predetermined time interval,wherein the second predetermined time interval is defined by a secondstart time and a second end time, wherein the second data structurestores transaction data associated with a payment transaction that isinitiated within the second predetermined time interval, wherein thesecond end time is after the first start time and before the first endtime, and the second end time is after the first end time, wherein thefirst data structure comprises a first overlap region and the seconddata structure comprises a second overlap region, wherein the firstoverlap region and the second overlap region are defined by an overlaptime interval, wherein the overlap time interval is defined between thesecond start time and the first end time; receiving, with at least oneprocessor, first transaction data associated with a first paymenttransaction, wherein the first transaction data comprises a firsttimestamp associated with initiation of the first payment transactionand a first transaction ID; determining, with at least one processor andbased on the first timestamp, that the first payment transaction fallswithin the overlap time interval; upon determining that the firstpayment transaction falls within the overlap time interval storing, withat least one processor, the first transaction data to the first datastructure and the second data structure; receiving, with at least oneprocessor, second transaction data associated with a second paymenttransaction, wherein the second transaction data comprises a secondtimestamp associated with initiation of the second payment transactionand a second transaction ID; determining, with at least one processorand based on the second timestamp, that the second payment transactionfalls within the overlap time interval; and upon determining that thesecond payment transaction falls within the overlap time interval,determining, with at least one processor and based on the firsttransaction ID and the second transaction ID, that the second paymenttransaction is a duplicate of the first payment transaction.

Clause 2: The method of clause 1, further comprising: upon determiningthat the second payment transaction is a duplicate of the first paymenttransaction, terminating, with at least one processor, processing of thesecond payment transaction.

Clause 3: The method of clause 1 or 2, further comprising: upondetermining that the second payment transaction is a duplicate of thefirst payment transaction, generating and communicating, with at leastone processor, a duplicate transaction response, wherein the duplicatetransaction response comprises data associated with identifying thesecond payment transaction as identical to the first paymenttransaction.

Clause 4: The method of any of the preceding clauses: upon determiningthat the second payment transaction is a duplicate of the first paymenttransaction, generating and communicating, with at least one processor,a duplicate transaction response, wherein the duplicate transactionresponse is identical to a response message communicated in connectionwith processing of the first payment transaction.

Clause 5: The method of any of the preceding clauses, wherein the firstdata structure and the second data structure are stored on separateservers.

Clause 6: The method of any of the preceding clauses, whereindetermining that the second payment transaction is a duplicate of thefirst payment transaction comprises receiving a return value in responseto a request to store the second transaction data.

Clause 7: The method of any of the preceding clauses, wherein upondetermining that the second payment transaction is a duplicate of thefirst payment transaction, initiating a fraudulent transactionsubmission protocol.

Clause 8: The method of any of the preceding clauses, wherein the firstpredetermined time interval and/or the second predetermined timeinterval comprises at least one month.

Clause 9: The method of any of the preceding clauses, wherein theoverlap time interval comprises from one minute to one day.

Clause 10: The method of any of the preceding clauses, wherein the firsttransaction data and/or second transaction data are received in the formof a transaction processing request message.

Clause 11: A computer program product for preventing duplicateprocessing of a payment transaction comprising at least onenon-transitory computer-readable medium including program instructionsthat, when executed by at least one computer including at least oneprocessor, causes the at least one computer to: generate a plurality ofdata structures, wherein generating the plurality of data structurescomprises: generating a first data structure associated with a firstunique identifier, wherein the first data structure is associated with afirst predetermined time interval, wherein the first predetermined timeinterval is defined by a first start time and a first end time, whereinthe first data structure stores transaction data associated with apayment transaction that is initiated within the first predeterminedtime interval; and generating a second data structure associated with asecond unique identifier, wherein the second data structure isassociated with a second predetermined time interval, wherein the secondpredetermined time interval is defined by a second start time and asecond end time, wherein the second data structure stores transactiondata associated with a payment transaction that is initiated within thesecond predetermined time interval, wherein the second end time is afterthe first start time and before the first end time, and the second endtime is after the first end time, wherein the first data structurecomprises a first overlap region and the second data structure comprisesa second overlap region, wherein the first overlap region and the secondoverlap region are defined by an overlap time interval, wherein theoverlap time interval is defined between the second start time and thefirst end time; receive first transaction data associated with a firstpayment transaction, wherein the first transaction data comprises afirst timestamp associated with initiation of the first paymenttransaction and a first transaction ID; determine based on the firsttimestamp, that the first payment transaction falls within the overlaptime interval; upon determining that the first payment transaction fallswithin the overlap time interval store the first transaction data to thefirst data structure and the second data structure; receive secondtransaction data associated with a second payment transaction, whereinthe second transaction data comprises a second timestamp associated withinitiation of the second payment transaction and a second transactionID; determine based on the second timestamp, that the second paymenttransaction falls within the overlap time interval; and upon determiningthat the second payment transaction falls within the overlap timeinterval, determine based on the first transaction ID and the secondtransaction ID, that the second payment transaction is a duplicate ofthe first payment transaction.

Clause 12: The computer program product of clause 11, wherein theprogram instructions are further configured to cause the at least onecomputer to: upon determining that the second payment transaction is aduplicate of the first payment transaction, terminate, with at least oneprocessor, processing of the second payment transaction.

Clause 13: The computer program product of clause 11 or 12, wherein theprogram instructions are further configured to cause the at least onecomputer to: upon determining that the second payment transaction is aduplicate of the first payment transaction, generate and communicate aduplicate transaction response, wherein the duplicate transactionresponse comprises data associated with identifying the second paymenttransaction as identical to the first payment transaction.

Clause 14: The computer program product of any of clauses 11-13, whereinthe program instructions are further configured to cause the at leastone computer to: upon determining that the second payment transaction isa duplicate of the first payment transaction, generate and communicate aduplicate transaction response, wherein the duplicate transactionresponse is identical to a response message communicated in connectionwith processing of the first payment transaction.

Clause 15: The computer program product of any of clauses 11-14, whereinthe first data structure and the second data structure are stored onseparate servers.

Clause 16: The computer program product of any of clauses 11-15, whereindetermining that the second payment transaction is a duplicate of thefirst payment transaction comprises receiving a return value in responseto a request to store the second transaction data.

Clause 17: The computer program product of any of clauses 11-16, whereinthe program instructions are further configured to cause the at leastone computer to: upon determining that the second payment transaction isa duplicate of the first payment transaction, initiate a fraudulenttransaction submission protocol.

Clause 18: The computer program product of any of clauses 11-17, whereinthe first predetermined time interval and/or the second predeterminedtime interval comprises at least one month.

Clause 19: The computer program product of any of clauses 11-18, whereinthe overlap time interval comprises from one minute to one day.

Clause 20: The computer program product of any of clauses 11-19, whereinthe first transaction data and/or second transaction data are receivedin the form of a transaction processing request message.

Clause 21: A system for preventing duplicate processing of a paymenttransaction comprising at least one server computer including at leastone processor, the at least one server computer programmed and/orconfigured to: generate a plurality of data structures, whereingenerating the plurality of data structures comprises: generating afirst data structure associated with a first unique identifier, whereinthe first data structure is associated with a first predetermined timeinterval, wherein the first predetermined time interval is defined by afirst start time and a first end time, wherein the first data structurestores transaction data associated with a payment transaction that isinitiated within the first predetermined time interval; and generating asecond data structure associated with a second unique identifier,wherein the second data structure is associated with a secondpredetermined time interval, wherein the second predetermined timeinterval is defined by a second start time and a second end time,wherein the second data structure stores transaction data associatedwith a payment transaction that is initiated within the secondpredetermined time interval, wherein the second end time is after thefirst start time and before the first end time, and the second end timeis after the first end time, wherein the first data structure comprisesa first overlap region and the second data structure comprises a secondoverlap region, wherein the first overlap region and the second overlapregion are defined by an overlap time interval, wherein the overlap timeinterval is defined between the second start time and the first endtime; receive first transaction data associated with a first paymenttransaction, wherein the first transaction data comprises a firsttimestamp associated with initiation of the first payment transactionand a first transaction ID; determine based on the first timestamp, thatthe first payment transaction falls within the overlap time interval;upon determining that the first payment transaction falls within theoverlap time interval store the first transaction data to the first datastructure and the second data structure; receive second transaction dataassociated with a second payment transaction, wherein the secondtransaction data comprises a second timestamp associated with initiationof the second payment transaction and a second transaction ID; determinebased on the second timestamp, that the second payment transaction fallswithin the overlap time interval; and upon determining that the secondpayment transaction falls within the overlap time interval, determinebased on the first transaction ID and the second transaction ID, thatthe second payment transaction is a duplicate of the first paymenttransaction.

Clause 22: The system of clause 21, wherein the at least one servercomputer is programmed and/or configured to: upon determining that thesecond payment transaction is a duplicate of the first paymenttransaction, terminate processing of the second payment transaction.

Clause 23: The system of clause 21 or 22, wherein the at least oneserver computer is programmed and/or configured to: upon determiningthat the second payment transaction is a duplicate of the first paymenttransaction, generate and communicate a duplicate transaction response,wherein the duplicate transaction response comprises data associatedwith identifying the second payment transaction as identical to thefirst payment transaction.

Clause 24: The system of any of clauses 21-23, wherein the at least oneserver computer is programmed and/or configured to: upon determiningthat the second payment transaction is a duplicate of the first paymenttransaction, generate and communicate a duplicate transaction response,wherein the duplicate transaction response is identical to a responsemessage communicated in connection with processing of the first paymenttransaction.

Clause 25: The system of any of clauses 21-24, wherein the first datastructure and the second data structure are stored on separate servers.

Clause 26: The system of any of clauses 21-25, wherein determining thatthe second payment transaction is a duplicate of the first paymenttransaction comprises receiving a return value in response to a requestto store the second transaction data.

Clause 27: The system of any of clauses 21-26, wherein the at least oneserver computer is programmed and/or configured to: upon determiningthat the second payment transaction is a duplicate of the first paymenttransaction, initiate a fraudulent transaction submission protocol.

Clause 28: The system of any of clauses 21-27, wherein the firstpredetermined time interval and/or the second predetermined timeinterval comprises at least one month.

Clause 29: The system of any of clauses 21-28, wherein the overlap timeinterval comprises from one minute to one day.

Clause 30: The system of any of clauses 21-29, wherein the firsttransaction data and/or second transaction data are received in the formof a transaction processing request message.

Clause 31: A method for preventing duplication of data processingcomprising: generating, with at least one processor, a plurality of datastructures, wherein generating the plurality of data structurescomprises: generating a first data structure associated with a firstunique identifier, wherein the first data structure is associated with afirst predetermined time interval, wherein the first predetermined timeinterval is defined by a first start time and a first end time, whereinthe first data structure stores data associated with the firstpredetermined time interval; and generating a second data structureassociated with a second unique identifier, wherein the second datastructure is associated with a second predetermined time interval,wherein the second predetermined time interval is defined by a secondstart time and a second end time, wherein the second data structurestores data associated with the second predetermined time interval,wherein the second end time is after the first start time and before thefirst end time, and the second end time is after the first end time,wherein the first data structure comprises a first overlap region andthe second data structure comprises a second overlap region, wherein thefirst overlap region and the second overlap region are defined by anoverlap time interval, wherein the overlap time interval is definedbetween the second start time and the first end time; receiving, with atleast one processor, first data comprising a first timestamp and a firstdata ID; determining, with at least one processor and based on the firsttimestamp, that the first data falls within the overlap time interval;upon determining that the first data falls within the overlap timeinterval storing, with at least one processor, the first data to thefirst data structure and the second data structure; receiving, with atleast one processor, second data comprising a second timestamp and asecond data ID; determining, with at least one processor and based onthe second timestamp, that the second data falls within the overlap timeinterval; and upon determining that the second data falls within theoverlap time interval, determining, with at least one processor andbased on the first data ID and the second data ID, that the second datais a duplicate of the first data.

Clause 32: The method of clause 31, further comprising: upon determiningthat the second data is a duplicate of the first data, terminating, withat least one processor, processing of the second data.

Clause 33: The method of clause 31 or 32, further comprising: upondetermining that the second data is a duplicate of the first data,generating and communicating, with at least one processor, a duplicatedata response, wherein the duplicate data response comprises dataassociated with identifying the second data as identical to the firstdata.

Clause 34: The method of any of clauses 31-33, further comprising: upondetermining that the second data is a duplicate of the first data,generating and communicating, with at least one processor, a duplicateresponse, wherein the duplicate response is identical to a responsemessage communicated in connection with processing of the first data.

Clause 35: The method of any of clauses 31-34, wherein the first datastructure and the second data structure are stored on separate servers.

Clause 36: The method of any of clauses 31-35, wherein determining thatthe second data is a duplicate of the first data comprises receiving areturn value in response to a request to store the second data.

Clause 37: A computer program product for preventing duplication of dataprocessing comprising at least one non-transitory computer-readablemedium including program instructions that, when executed by at leastone computer including at least one processor, causes the at least onecomputer to: generate a plurality of data structures, wherein generatingthe plurality of data structures comprises: generating a first datastructure associated with a first unique identifier, wherein the firstdata structure is associated with a first predetermined time interval,wherein the first predetermined time interval is defined by a firststart time and a first end time, wherein the first data structure storesdata associated with the first predetermined time interval; andgenerating a second data structure associated with a second uniqueidentifier, wherein the second data structure is associated with asecond predetermined time interval, wherein the second predeterminedtime interval is defined by a second start time and a second end time,wherein the second data structure stores data associated with the secondpredetermined time interval, wherein the second end time is after thefirst start time and before the first end time, and the second end timeis after the first end time, wherein the first data structure comprisesa first overlap region and the second data structure comprises a secondoverlap region, wherein the first overlap region and the second overlapregion are defined by an overlap time interval, wherein the overlap timeinterval is defined between the second start time and the first endtime; receive first data comprising a first timestamp and a first dataID; determine based on the first timestamp, that the first data fallswithin the overlap time interval; upon determining that the first datafalls within the overlap time interval store the first data to the firstdata structure and the second data structure; receive second datacomprising a second timestamp and a second data ID; determine based onthe second timestamp, that the second data falls within the overlap timeinterval; and upon determining that the second data falls within theoverlap time interval, determine based on the first data ID and thesecond data ID, that the second data is a duplicate of the first data.

Clause 38: The computer program product of clause 37, wherein theprogram instructions are further configured to cause the at least onecomputer to: upon determining that the second data is a duplicate of thefirst data, terminate processing of the second data.

Clause 39: The computer program product of clause 37 or 38, wherein theprogram instructions are further configured to cause the at least onecomputer to: upon determining that the second data is a duplicate of thefirst data, generate and communicate a duplicate data response, whereinthe duplicate data response comprises data associated with identifyingthe second data as identical to the first data.

Clause 40: The computer program product of any of clauses 37-39, whereinthe program instructions are further configured to cause the at leastone computer to: upon determining that the second data is a duplicate ofthe first data, generate and communicate, with at least one processor, aduplicate response, wherein the duplicate response is identical to aresponse message communicated in connection with processing of the firstdata.

Clause 41: The computer program product of any of clauses 37-40, whereinthe first data structure and the second data structure are stored onseparate servers.

Clause 42: The computer program product of any of clauses 37-41,determining that the second data is a duplicate of the first datacomprises receiving a return value in response to a request to store thesecond data.

Clause 43: A system for preventing duplication of data processingcomprising at least one server computer including at least oneprocessor, the at least one server computer programmed and/or configuredto: generate a plurality of data structures, wherein generating theplurality of data structures comprises: generating a first datastructure associated with a first unique identifier, wherein the firstdata structure is associated with a first predetermined time interval,wherein the first predetermined time interval is defined by a firststart time and a first end time, wherein the first data structure storesdata associated with the first predetermined time interval; andgenerating a second data structure associated with a second uniqueidentifier, wherein the second data structure is associated with asecond predetermined time interval, wherein the second predeterminedtime interval is defined by a second start time and a second end time,wherein the second data structure stores data associated with the secondpredetermined time interval, wherein the second end time is after thefirst start time and before the first end time, and the second end timeis after the first end time, wherein the first data structure comprisesa first overlap region and the second data structure comprises a secondoverlap region, wherein the first overlap region and the second overlapregion are defined by an overlap time interval, wherein the overlap timeinterval is defined between the second start time and the first endtime; receive first data comprising a first timestamp and a first dataID; determine based on the first timestamp, that the first data fallswithin the overlap time interval; upon determining that the first datafalls within the overlap time interval store the first data to the firstdata structure and the second data structure; receive second datacomprising a second timestamp and a second data ID; determine based onthe second timestamp, that the second data falls within the overlap timeinterval; and upon determining that the second data falls within theoverlap time interval, determine based on the first data ID and thesecond data ID, that the second data is a duplicate of the first data.

Clause 44: The system of clause 43, wherein the at least one servercomputer is programmed and/or configured to: upon determining that thesecond data is a duplicate of the first data, terminate processing ofthe second data.

Clause 45: The system of clause 43 or 44, wherein the at least oneserver computer is programmed and/or configured to: upon determiningthat the second data is a duplicate of the first data, generate andcommunicate a duplicate data response, wherein the duplicate dataresponse comprises data associated with identifying the second data asidentical to the first data.

Clause 46: The system of any of clauses 43-45, wherein the at least oneserver computer is programmed and/or configured to: upon determiningthat the second data is a duplicate of the first data, generate andcommunicate, with at least one processor, a duplicate response, whereinthe duplicate response is identical to a response message communicatedin connection with processing of the first data.

Clause 47: The system of any of clauses 43-46, wherein the first datastructure and the second data structure are stored on separate servers.

Clause 48: The system of any of clauses 43-47, wherein determining thatthe second data is a duplicate of the first data comprises receiving areturn value in response to a request to store the second data.

Clause 49: A method for preventing duplicate processing of a tokenassigned for temporary use comprising: generating, with at least oneprocessor, a plurality of data structures, wherein generating theplurality of data structures comprises: generating a first datastructure associated with a first unique identifier, wherein the firstdata structure is associated with a first predetermined time interval,wherein the first predetermined time interval is defined by a firststart time and a first end time, wherein the first data structure storestoken data associated with a temporary token generated within the firstpredetermined time interval; and generating a second data structureassociated with a second unique identifier, wherein the second datastructure is associated with a second predetermined time interval,wherein the second predetermined time interval is defined by a secondstart time and a second end time, wherein the second data structurestores token data associated with a temporary token generated within thesecond predetermined time interval, wherein the second end time is afterthe first start time and before the first end time, and the second endtime is after the first end time, wherein the first data structurecomprises a first overlap region and the second data structure comprisesa second overlap region, wherein the first overlap region and the secondoverlap region are defined by an overlap time interval, wherein theoverlap time interval is defined between the second start time and thefirst end time; receiving, with at least one processor, first token dataassociated with a first token, wherein the first token data comprises afirst timestamp associated with generation of the first token and afirst token ID; determining, with at least one processor and based onthe first timestamp, that the first timestamp falls within the overlaptime interval; upon determining that the first timestamp falls withinthe overlap time interval storing, with at least one processor, thefirst token data to the first data structure and the second datastructure; receiving, with at least one processor, second token dataassociated with a second token, wherein the second token comprises asecond timestamp associated with generation of the second token and asecond token ID; determining, with at least one processor and based onthe second timestamp, that the second timestamp falls within the overlaptime interval; and upon determining that the second timestamp fallswithin the overlap time interval, determining, with at least oneprocessor and based on the first token ID and the second token ID, thatthe second token is a duplicate of the first token.

Clause 50: The method of clause 49, further comprising: determiningwhether the first token and/or the second token are expired.

Clause 51: The method of clause 49 or 50, further comprising: upondetermining that the second token is a duplicate of the first token,terminating, with at least one processor, processing of the secondtoken.

Clause 52: The method of any of clauses 49-51, further comprising: upondetermining that the second token is a duplicate of the first token,generating and communicating, with at least one processor, a duplicatetoken response, wherein the duplicate token response comprises dataassociated with identifying the second token as identical to the firsttoken.

Clause 53: The method of any of clauses 49-52, further comprising: upondetermining that the second token is a duplicate of the first token,generating and communicating, with at least one processor, a duplicatetoken response, wherein the duplicate token response is identical to aresponse message communicated in connection with processing of the firsttoken.

Clause 54: The method of any of clauses 49-53, wherein the first datastructure and the second data structure are stored on separate servers.

Clause 55: The method of any of clauses 49-54, wherein determining thatthe second token is a duplicate of the first token comprises receiving areturn value in response to a request to store the second token data.

Clause 56: The method of any of clauses 49-55, wherein upon determiningthat the second token is a duplicate of the first token, initiating afraudulent token submission protocol.

Clause 57: The method of any of clauses 49-56, wherein the firstpredetermined time interval and/or the second predetermined timeinterval comprises at least one month.

Clause 58: The method of any of clauses 49-57, wherein the overlap timeinterval comprises from one minute to one day.

Clause 59: The method of any of clauses 49-58, wherein the first tokendata and/or second token data are received in the form of a tokenprocessing request message.

Clause 60: A system for preventing duplicate processing of a tokenassigned for temporary use comprising at least one server computerincluding at least one processor, the at least one server computerprogrammed and/or configured to: generate a plurality of datastructures, wherein generating the plurality of data structurescomprises: generating a first data structure associated with a firstunique identifier, wherein the first data structure is associated with afirst predetermined time interval, wherein the first predetermined timeinterval is defined by a first start time and a first end time, whereinthe first data structure stores token data associated with a temporarytoken generated within the first predetermined time interval; andgenerating a second data structure associated with a second uniqueidentifier, wherein the second data structure is associated with asecond predetermined time interval, wherein the second predeterminedtime interval is defined by a second start time and a second end time,wherein the second data structure stores token data associated with atemporary token generated within the second predetermined time interval,wherein the second end time is after the first start time and before thefirst end time, and the second end time is after the first end time,wherein the first data structure comprises a first overlap region andthe second data structure comprises a second overlap region, wherein thefirst overlap region and the second overlap region are defined by anoverlap time interval, wherein the overlap time interval is definedbetween the second start time and the first end time; receive firsttoken data associated with a first token, wherein the first token datacomprises a first timestamp associated with generation of the firsttoken and a first token ID; determine based on the first timestamp, thatthe first timestamp falls within the overlap time interval; upondetermining that the first timestamp falls within the overlap timeinterval, store the first token data to the first data structure and thesecond data structure; receive second token data associated with asecond token, wherein the second token comprises a second timestampassociated with generation of the second token and a second token ID;determine based on the second timestamp, that the second timestamp fallswithin the overlap time interval; and upon determining that the secondtimestamp falls within the overlap time interval, determine based on thefirst token ID and the second token ID, that the second token is aduplicate of the first token.

Clause 61: A method for preventing duplicate processing of a passwordassigned for temporary use comprising: generating, with at least oneprocessor, a plurality of data structures, wherein generating theplurality of data structures comprises: generating a first datastructure associated with a first unique identifier, wherein the firstdata structure is associated with a first predetermined time interval,wherein the first predetermined time interval is defined by a firststart time and a first end time, wherein the first data structure storespassword data associated with a temporary password generated within thefirst predetermined time interval; and generating a second datastructure associated with a second unique identifier, wherein the seconddata structure is associated with a second predetermined time interval,wherein the second predetermined time interval is defined by a secondstart time and a second end time, wherein the second data structurestores password data associated with a temporary password generatedwithin the second predetermined time interval, wherein the second endtime is after the first start time and before the first end time, andthe second end time is after the first end time, wherein the first datastructure comprises a first overlap region and the second data structurecomprises a second overlap region, wherein the first overlap region andthe second overlap region are defined by an overlap time interval,wherein the overlap time interval is defined between the second starttime and the first end time; receiving, with at least one processor,first password data associated with a first password, wherein the firstpassword data comprises a first timestamp associated with generation ofthe first password; determining, with at least one processor and basedon the first timestamp, that the first timestamp falls within theoverlap time interval; upon determining that the first timestamp fallswithin the overlap time interval storing, with at least one processor,the first password data to the first data structure and the second datastructure; receiving, with at least one processor, second password dataassociated with a second password, wherein the second password comprisesa second timestamp associated with generation of the second password;determining, with at least one processor and based on the secondtimestamp, that the second timestamp falls within the overlap timeinterval; and upon determining that the second timestamp falls withinthe overlap time interval, determining, with at least one processor andbased on the first password and the second password, that the secondpassword is a duplicate of the first password.

Clause 62: The method of clause 61, further comprising: determiningwhether the first password and/or the second password are expired.

Clause 63: The method of clause 61 or 62, further comprising: upondetermining that the second password is a duplicate of the firstpassword, terminating, with at least one processor, processing of thesecond password.

Clause 64: The method of any of clauses 61-63, further comprising: upondetermining that the second password is a duplicate of the firstpassword, generating and communicating, with at least one processor, aduplicate password response, wherein the duplicate password responsecomprises data associated with identifying the second password asidentical to the first password.

Clause 65: The method of any of clauses 61-64, further comprising: upondetermining that the second password is a duplicate of the firstpassword, generating and communicating, with at least one processor, aduplicate password response, wherein the duplicate password response isidentical to a response message communicated in connection withprocessing of the first password.

Clause 66: The method of any of clauses 61-65, wherein the first datastructure and the second data structure are stored on separate servers.

Clause 67: The method of any of clauses 61-66, wherein determining thatthe second password is a duplicate of the first password comprisesreceiving a return value in response to a request to store the secondpassword data.

Clause 68: The method of any of clauses 61-67, wherein upon determiningthat the second password is a duplicate of the first password,initiating a fraudulent password submission protocol.

Clause 69: The method of any of clauses 61-68, wherein the firstpredetermined time interval and/or the second predetermined timeinterval comprises at least one month.

Clause 70: The method of any of clauses 61-69, wherein the overlap timeinterval comprises from one minute to one day.

Clause 71: The method of any of clauses 61-70, wherein the firstpassword data and/or second password data are received in the form of apassword processing request message.

Clause 72: A system for preventing duplicate processing of a passwordassigned for temporary use comprising at least one server computerincluding at least one processor, the at least one server computerprogrammed and/or configured to: generate a plurality of datastructures, wherein generating the plurality of data structurescomprises: generating a first data structure associated with a firstunique identifier, wherein the first data structure is associated with afirst predetermined time interval, wherein the first predetermined timeinterval is defined by a first start time and a first end time, whereinthe first data structure stores password data associated with atemporary password generated within the first predetermined timeinterval; and generating a second data structure associated with asecond unique identifier, wherein the second data structure isassociated with a second predetermined time interval, wherein the secondpredetermined time interval is defined by a second start time and asecond end time, wherein the second data structure stores password dataassociated with a temporary password generated within the secondpredetermined time interval, wherein the second end time is after thefirst start time and before the first end time, and the second end timeis after the first end time, wherein the first data structure comprisesa first overlap region and the second data structure comprises a secondoverlap region, wherein the first overlap region and the second overlapregion are defined by an overlap time interval, wherein the overlap timeinterval is defined between the second start time and the first endtime; receive first password data associated with a first password,wherein the first password data comprises a first timestamp associatedwith generation of the first password; determine based on the firsttimestamp, that the first timestamp falls within the overlap timeinterval; upon determining that the first timestamp falls within theoverlap time interval, store the first password data to the first datastructure and the second data structure; receive second password dataassociated with a second password, wherein the second password comprisesa second timestamp associated with generation of the second password;determine based on the second timestamp, that the second timestamp fallswithin the overlap time interval; and upon determining that the secondtimestamp falls within the overlap time interval, determine based on thefirst password and the second password, that the second password is aduplicate of the first password.

Clause 73: A method for preventing duplicate processing of an offerissued for temporary redemption comprising: generating, with at leastone processor, a plurality of data structures, wherein generating theplurality of data structures comprises: generating a first datastructure associated with a first unique identifier, wherein the firstdata structure is associated with a first predetermined time interval,wherein the first predetermined time interval is defined by a firststart time and a first end time, wherein the first data structure storesoffer data associated with a temporary offer issued within the firstpredetermined time interval; and generating a second data structureassociated with a second unique identifier, wherein the second datastructure is associated with a second predetermined time interval,wherein the second predetermined time interval is defined by a secondstart time and a second end time, wherein the second data structurestores offer data associated with a temporary offer issued within thesecond predetermined time interval, wherein the second end time is afterthe first start time and before the first end time, and the second endtime is after the first end time, wherein the first data structurecomprises a first overlap region and the second data structure comprisesa second overlap region, wherein the first overlap region and the secondoverlap region are defined by an overlap time interval, wherein theoverlap time interval is defined between the second start time and thefirst end time; receiving, with at least one processor, first offer dataassociated with a first offer, wherein the first offer data comprises afirst timestamp associated with issuance of the first offer and a firstoffer ID; determining, with at least one processor and based on thefirst timestamp, that the first timestamp falls within the overlap timeinterval; upon determining that the first timestamp falls within theoverlap time interval storing, with at least one processor, the firstoffer data to the first data structure and the second data structure;receiving, with at least one processor, second offer data associatedwith a second offer, wherein the second offer comprises a secondtimestamp associated with issuance of the second offer and a secondoffer ID; determining, with at least one processor and based on thesecond timestamp, that the second timestamp falls within the overlaptime interval; and upon determining that the second timestamp fallswithin the overlap time interval, determining, with at least oneprocessor and based on the first offer ID and the second offer ID, thatthe second offer is a duplicate of the first offer.

Clause 74: The method of clause 73, further comprising: determiningwhether the first offer and/or the second offer are expired.

Clause 75: The method of clause 73 or 74, further comprising: upondetermining that the second offer is a duplicate of the first offer,terminating, with at least one processor, processing of the secondoffer.

Clause 76: The method of any of clauses 73-75, further comprising: upondetermining that the second offer is a duplicate of the first offer,generating and communicating, with at least one processor, a duplicateoffer response, wherein the duplicate offer response comprises dataassociated with identifying the second offer as identical to the firstoffer.

Clause 77: The method of any of clauses 73-76, further comprising: upondetermining that the second offer is a duplicate of the first offer,generating and communicating, with at least one processor, a duplicateoffer response, wherein the duplicate offer response is identical to aresponse message communicated in connection with processing of the firstoffer.

Clause 78: The method of any of clauses 73-77, wherein the first datastructure and the second data structure are stored on separate servers.

Clause 79: The method of any of clauses 73-78, wherein determining thatthe second offer is a duplicate of the first offer comprises receiving areturn value in response to a request to store the second offer.

Clause 80: The method of any of clauses 73-79, wherein upon determiningthat the second offer is a duplicate of the first offer, initiating afraudulent offer redemption protocol.

Clause 81: The method of any of clauses 73-80, wherein the firstpredetermined time interval and/or the second predetermined timeinterval comprises at least one month.

Clause 82: The method of any of clauses 73-81, wherein the overlap timeinterval comprises from one minute to one day.

Clause 83: The method of any of clauses 73-82, wherein the first offerdata and/or second offer data are received in the form of an offerprocessing request message.

Clause 84: A system for preventing duplicate processing of an offerissued for temporary redemption comprising at least one server computerincluding at least one processor, the at least one server computerprogrammed and/or configured to: generate a plurality of datastructures, wherein generating the plurality of data structurescomprises: generating a first data structure associated with a firstunique identifier, wherein the first data structure is associated with afirst predetermined time interval, wherein the first predetermined timeinterval is defined by a first start time and a first end time, whereinthe first data structure stores offer data associated with a temporaryoffer generated within the first predetermined time interval; andgenerating a second data structure associated with a second uniqueidentifier, wherein the second data structure is associated with asecond predetermined time interval, wherein the second predeterminedtime interval is defined by a second start time and a second end time,wherein the second data structure stores offer data associated with atemporary offer issued within the second predetermined time interval,wherein the second end time is after the first start time and before thefirst end time, and the second end time is after the first end time,wherein the first data structure comprises a first overlap region andthe second data structure comprises a second overlap region, wherein thefirst overlap region and the second overlap region are defined by anoverlap time interval, wherein the overlap time interval is definedbetween the second start time and the first end time; receive firstoffer data associated with a first offer, wherein the first offer datacomprises a first timestamp associated with issuance of the first offerand a first offer ID; determine based on the first timestamp, that thefirst timestamp falls within the overlap time interval; upon determiningthat the first timestamp falls within the overlap time interval, storethe first offer data to the first data structure and the second datastructure; receive second offer data associated with a second offer,wherein the second offer comprises a second timestamp associated withgeneration of the second offer and a second offer ID; determine based onthe second timestamp, that the second timestamp falls within the overlaptime interval; and upon determining that the second timestamp fallswithin the overlap time interval, determine based on the first offer IDand the second offer ID, that the second offer is a duplicate of thefirst offer.

BRIEF DESCRIPTION OF THE DRAWINGS

Additional advantages and details of the invention are explained ingreater detail below with reference to the exemplary embodiments thatare illustrated in the accompanying schematic figures, in which:

FIG. 1 shows a schematic diagram of a plurality of data structuresaccording to the present invention;

FIG. 2 shows a schematic diagram of a system for preventing duplicateprocessing of data according to the present invention;

FIG. 3 shows another schematic diagram of a system for preventingduplicate processing of data according to the present invention;

FIG. 4 shows a step diagram of a method for preventing duplicateprocessing of data according to the present invention;

FIG. 5 shows a step diagram of a method for preventing duplicateprocessing of a payment transaction according to the present invention;

FIG. 6 shows a data structure for data associated with a paymenttransaction according to the present invention;

FIG. 7A shows a schematic diagram of a system for preventing duplicateprocessing of a payment transaction, the system processing a firstrequest for processing the payment transaction according to the presentinvention;

FIG. 7B shows a schematic diagram of a system for preventing duplicateprocessing of a payment transaction, the system processing a secondduplicate request for processing the payment transaction according tothe present invention;

FIG. 8 shows a step diagram of a method for preventing duplicateprocessing of a token assigned for temporary use according to thepresent invention;

FIG. 9 shows a data structure for data associated with a token assignedfor temporary use according to the present invention;

FIG. 10A shows a schematic diagram of a system for preventing duplicateprocessing of a token assigned for temporary use, the system processinga first request for processing the token according to the presentinvention;

FIG. 10B shows a schematic diagram of a system for preventing duplicateprocessing of a token assigned for temporary use, the system processinga second duplicate request for processing the token according to thepresent invention;

FIG. 11 shows a step diagram of a method for preventing duplicateprocessing of a password assigned for temporary use according to thepresent invention;

FIG. 12 shows a data structure for data associated with a passwordassigned for temporary use according to the present invention;

FIG. 13A shows a schematic diagram of a login screen for processing of apassword assigned for temporary use, the system processing a firstrequest for processing the password according to the present invention;

FIG. 13B shows a schematic diagram of a login screen for preventingduplicate processing of a password assigned for temporary use, thesystem processing a second duplicate request for processing the passwordaccording to the present invention;

FIG. 14 shows a step diagram of a method for preventing duplicateprocessing of an offer issued for temporary use according to the presentinvention;

FIG. 15 shows a data structure for data associated with an offer issuedfor temporary use according to the present invention;

FIG. 16A shows a schematic diagram of a system for preventing duplicateprocessing of an offer issued for temporary use, the system processing afirst request for processing the offer according to the presentinvention;

FIG. 16B shows a schematic diagram of a system for preventing duplicateprocessing of an offer assigned for temporary use, the system processinga second duplicate request for processing the offer according to thepresent invention; and

FIG. 17 shows a process flow diagram of a method for preventingduplicate processing of data according to the present invention.

DESCRIPTION OF THE INVENTION

For purposes of the description hereinafter, the terms “end,” “upper,”“lower,” “right,” “left,” “vertical,” “horizontal,” “top,” “bottom,”“lateral,” “longitudinal,” and derivatives thereof shall relate to theinvention as it is oriented in the drawing figures. However, it is to beunderstood that the invention may assume various alternative variationsand step sequences, except where expressly specified to the contrary. Itis also to be understood that the specific devices and processesillustrated in the attached drawings, and described in the followingspecification, are simply exemplary embodiments or aspects of theinvention. Hence, specific dimensions and other physical characteristicsrelated to the embodiments or aspects disclosed herein are not to beconsidered as limiting.

As used herein, the terms “communication” and “communicate” may refer tothe reception, receipt, transmission, transfer, provision, and/or thelike, of information (e.g., data, signals, messages, instructions,commands, and/or the like). For one unit (e.g., a device, a system, acomponent of a device or system, combinations thereof, and/or the like)to be in communication with another unit means that the one unit is ableto directly or indirectly receive information from and/or transmitinformation to the other unit. This may refer to a direct or indirectconnection (e.g., a direct communication connection, an indirectcommunication connection, and/or the like) that is wired and/or wirelessin nature. Additionally, two units may be in communication with eachother even though the information transmitted may be modified,processed, relayed, and/or routed between the first and second unit. Forexample, a first unit may be in communication with a second unit eventhough the first unit passively receives information and does notactively transmit information to the second unit. As another example, afirst unit may be in communication with a second unit if at least oneintermediary unit (e.g., a third unit located between the first unit andthe second unit) processes information received from the first unit andcommunicates the processed information to the second unit. In somenon-limiting embodiments, a message may refer to a network packet (e.g.,a data packet, and/or the like) that includes data. It will beappreciated that numerous other arrangements are possible.

As used herein, the term “transaction service provider” may refer to anentity that receives transaction authorization requests from merchantsor other entities and provides guarantees of payment, in some casesthrough an agreement between the transaction service provider and anissuer institution. For example, a transaction service provider mayinclude a payment network such as Visa® or any other entity thatprocesses transactions. The term “transaction processing server” mayrefer to one or more computer systems operated by or on behalf of atransaction service provider, such as a transaction processing serverexecuting one or more software applications. A transaction processingserver may include one or more processors and, in some non-limitingembodiments, may be operated by or on behalf of a transaction serviceprovider.

As used herein, the term “issuer institution” may refer to one or moreentities, such as a bank, that provide accounts to customers forconducting transactions (e.g., payment transactions), such as initiatingcredit and/or debit payments. For example, an issuer institution mayprovide an account identifier, such as a personal account number (PAN),to a customer that uniquely identifies one or more accounts associatedwith that customer. The account identifier may be embodied on a portablefinancial device, such as a physical financial instrument, e.g., apayment card, and/or may be electronic and used for electronic payments.The term “issuer system” or “issuer server” refers to one or morecomputer systems operated by or on behalf of an issuer institution, suchas a server computer executing one or more software applications. Forexample, an issuer system may include one or more authorization serversfor authorizing a transaction.

As used herein, the term “account identifier” may include one or morePANs, tokens, or other identifiers associated with a customer account.The term “token” may refer to an identifier that is used as a substituteor replacement identifier for an original account identifier, such as aPAN. Account identifiers may be alphanumeric or any combination ofcharacters and/or symbols. Tokens may be associated with a PAN or otheroriginal account identifier in one or more data structures (e.g., one ormore databases, and/or the like) that may be used to conduct atransaction without directly using the original account identifier. Insome examples, an original account identifier, such as a PAN, may beassociated with a plurality of tokens for different individuals orpurposes.

As used herein, the term “merchant” may refer to an individual or entitythat provides goods and/or services, or access to goods and/or services,to customers based on a transaction, such as a payment transaction. Theterm “merchant” or “merchant system” may also refer to one or morecomputer systems operated by or on behalf of a merchant, such as aserver computer executing one or more software applications. A“point-of-sale (POS) system,” as used herein, may refer to one or morecomputers and/or peripheral devices used by a merchant to engage inpayment transactions with customers, including one or more card readers,near-field communication (NFC) receivers, RFID receivers, and/or othercontactless transceivers or receivers, contact-based receivers, paymentterminals, computers, servers, input devices, and/or other like devicesthat can be used to initiate a payment transaction.

As used herein, the term “mobile device” may refer to one or moreportable electronic devices configured to communicate with one or morenetworks. As an example, a mobile device may include a cellular phone(e.g., a smartphone or standard cellular phone), a portable computer(e.g., a tablet computer, a laptop computer, etc.), a wearable device(e.g., a watch, pair of glasses, lens, clothing, and/or the like), apersonal digital assistant (PDA), and/or other like devices. The term“client device,” as used herein, refers to any electronic device that isconfigured to communicate with one or more servers or remote devicesand/or systems. A client device may include a mobile device, anetwork-enabled appliance (e.g., a network-enabled television,refrigerator, thermostat, and/or the like), a computer, a POS system,and/or any other device or system capable of communicating with anetwork.

As used herein, the term “computing device” may refer to one or moreelectronic devices that are configured to directly or indirectlycommunicate with or over one or more networks. The computing device maybe a mobile device. In other non-limiting embodiments, the computingdevice may be a desktop computer or other non-mobile computer.Furthermore, the term “computer” may refer to any computing device thatincludes the necessary components to receive, process, and output data,and normally includes a display, a processor, a memory, an input device,and a network interface. An “application” or “application programinterface” (API) refers to computer code or other data sorted on acomputer-readable medium that may be executed by a processor tofacilitate the interaction between software components, such as aclient-side front-end and/or server-side back-end for receiving datafrom the client. An “interface” refers to a generated display, such asone or more graphical user interfaces (GUIs) with which a user mayinteract, either directly or indirectly (e.g., through a keyboard,mouse, etc.).

As used herein, the term “portable financial device” may refer to apayment card (e.g., a credit or debit card), a gift card, a smartcard,smart media, a payroll card, a healthcare card, a wrist band, amachine-readable medium containing account information, a keychaindevice or fob, an RFID transponder, a retailer discount or loyalty card,a cellular phone, an electronic wallet mobile application, a personaldigital assistant (PDA), a pager, a security card, a computer, an accesscard, a wireless terminal, a transponder, and/or the like. In somenon-limiting embodiments, the portable financial device may includevolatile or non-volatile memory to store information (e.g., an accountidentifier, a name of the account holder, and/or the like).

The term “account data,” as used herein, refers to any data concerningone or more accounts for one or more users. Account data may include,for example, one or more account identifiers, user identifiers,transaction histories, balances, credit limits, issuer institutionidentifiers, and/or the like.

As used herein, the term “server” may refer to or include one or moreprocessors or computers, storage devices, or similar computerarrangements that are operated by or facilitate communication andprocessing for multiple parties in a network environment, such as theinternet, although it will be appreciated that communication may befacilitated over one or more public or private network environments andthat various other arrangements are possible. Further, multiplecomputers, e.g., servers, or other computerized devices, e.g.,point-of-sale devices, directly or indirectly communicating in thenetwork environment may constitute a “system,” such as a merchant'spoint-of-sale system. Reference to “a server” or “a processor,” as usedherein, may refer to a previously-recited server and/or processor thatis recited as performing a previous step or function, a different serverand/or processor, and/or a combination of servers and/or processors. Forexample, as used in the specification and the claims, a first serverand/or a first processor that is recited as performing a first step orfunction may refer to the same or different server and/or a processorrecited as performing a second step or function.

Non-limiting embodiments or aspects of the present invention aredirected to a method, system and computer program product for preventingduplication of data processing. Non-limiting embodiments or aspects ofthe invention include a plurality of data structures for storing data,with temporally consecutive data structures including at least oneoverlap time interval defined between the start time of the second datastructure and the end time of the first data structure. The overlap timeinterval accounts for the potential for data that was intended to beassociated with a first time being instead associated with a second timebecause, for instance, a system malfunction during the first timeprevented the data from being associated with the first time. In thisway, the overlap time interval allows for data at the edge of a datastructure (e.g., data at the edge of a data structure that includes dataassociated with an event, data at the edge of a data structure thatincludes data associated with a request, and/or the like) to still becaptured within the overlap time interval of that data structure. Bycapturing data at the edge of a data structure within the overlap timeinterval, a computer system can prevent the failure to identify arequest as a duplicate request to process the same data and preventduplicate processing of the data.

In addition, segmenting of the data as in the present inventionincreases efficiency of the computer system and reduces processing timeto determine whether there is potentially duplicate data. Embodiments ofthe present invention also save hardware costs for the computer systemas data structures having less storage capacity may not be as costly asdata structures having large storage capacity to function as a globaldata structure for storing all data. Embodiments of the presentinvention also provide a solution for systems in which large quantitiesof data are generated and stored that may exceed the potential storagecapacity of any single global data structure. Therefore, embodiments ofthe present invention increases the efficiency of the computer systemand ensures that duplicate requests to process data are recognized sothat resources of the computer system are not used to re-process thedata.

Referring to FIG. 1, a non-limiting embodiment or aspect of a system 10including a plurality of data structures is shown according to thepresent invention. The system may include a first data structure 12having a first unique identifier 13, a second data structure 14 having asecond unique identifier 15, a third data structure 16 have a thirdunique identifier 17, and so forth, such that the system 10 includes ndata structures, each data structure having a unique identifier. Theunique identifier of each data structure allows each data structure tobe identified using only that unique identifier. The unique identifierof each data structure is different from the unique identifierassociated with any other data structure in the system 10. The system 10includes at least two data structures (the first data structure 12 andthe second data structure 14). The data structures may be storagedevices, such as databases, configured to store electronic data. Datamay include any information capable of being stored and transmitted. Thedata may be associated with any number of activities, including, but notlimited to, payment transactions, tokens issued for temporary use inconnection with a payment transaction, a password issued for temporaryuse in connection with a user account, an offer issued for temporary useredeemable with a payment transaction, and the like.

With continued reference to FIG. 1, the system may define a firstpredetermined time interval (T₁) 18, a second predetermined timeinterval (T₂) 20, and a third predetermined time interval (T₃) 22. T₁-T₃may be temporally consecutive such that there is no time gap between T₁and T₂ and between T₂ and T₃. The first data structure 12 (and T₁) maybe defined between a first start time 24 and a first end time 26, suchthat the first data structure 12 may store data associated with a timebetween the first start time 24 and the first end time 26. The seconddata structure 14 (and T₂) may be defined between a second start time 28and a second end time 30, such that the second data structure 14 maystore data associated with a time between the second start time 28 andthe second end time 30. The third data structure 16 (and T₃) may bedefined between a third start time 32 and a third end time 34, such thatthe third data structure 16 may store data associated with a timebetween the third start time 32 and the third end time 34.

With continued reference to FIG. 1, the second start time 28 may beafter the first start time 24 but before the first end time 26. In thisway, an overlap region is created in the first data structure 12 and thesecond data structure 14, which is defined as an overlap region (n₁) 36(an overlap time interval). Data associated with a time in this overlapregion 36 may be stored in both the first data structure 12 and thesecond data structure 14. Similarly, the third start time 32 may beafter the second start time 28 but before the second end time 30. Inthis way, an overlap region is created in the second data structure 14and the third data structure 16, which is defined as an overlap region(n₂) 38. Data associated with a time in this overlap region 38 may bestored in both the second data structure 14 and the third data structure16. The overlap regions 36, 38 may be defined proximate the “edge” of atleast one of the data structures, such that the edge region includes thefirst and/or the last data entries stored in one of the data structures.

Referring to FIG. 2, a system 40 for preventing duplicate processing ofdata is shown. The system 40 may include a requesting device 42. Therequesting device 42 may be a computing device. The requesting device 42may be capable of communicating requests for data to be processed. Thesystem 40 may also include a request processor 44. The request processor44 may be a single processor or multiple processors capable of receivingrequests from the requesting device 42, processing those requests, andcommunicating a response to the requesting device 42 based on theprocessing of the request.

With continued reference to FIG. 2, the request processor 44 may be incommunication with a plurality of servers. For example, the requestprocessor 44 may be in communication with a first server 46, a secondserver 48, and a third server 50 (and any other number of servers). Theservers and the request processor 44 may be components of the samesystem or may be components of separate systems.

Each server may include a plurality of data structures 52. The pluralityof data structures 52 may be as described above in connection withFIG. 1. In one non-limiting example, the first data structure 12 may bestored on the first server 46, while the second data structure 14 may bestored on the second server 48.

With reference to FIG. 3, a system 60 for preventing duplicateprocessing of data is shown that is identical to FIG. 2 except that itincludes on a single server 62 including a plurality of data structures52. In this example, the first data structure 12 and the second datastructure 14 are stored on the same server 62 (instead of two separateservers as in FIG. 2).

Referring to FIG. 4 a method 100 for preventing duplicate processing ofdata is shown. At a first step 102, a processor generates the pluralityof data structures 52 (including the first data structure 12 and thesecond data structure 14). The first data structure 12 and the seconddata structure 14 are as previously described and include the overlapregion 36.

With continued reference to FIG. 4, at a second step 104 a processorreceives first data including a first timestamp and a first data ID. Thefirst timestamp may be associated with the time the data was generated,received, processed, transmitted, or any other event associated with thedata. In one example, the timestamp will specify the time at which thefirst data was received and associated with the first data ID. In otherexamples, the first data ID will have been associated with the firstdata prior to receiving the first data, such as the first timestampreflecting a time at which the same or different system received,generated, etc. the first data. The first data ID may be a uniqueidentifier that allows the first data to be identified solely based onthat first data ID. The first data ID may be different from the data IDof any other data having a data ID. The first data ID may be anysequence of numbers, characters, symbols, and the like. For example, thefirst data ID may be a numerical count that increments by a value of oneupon the receipt/generation of new data. In another example, the firstdata ID may be a randomly generated sequence generated at the time thedata is received/generated.

With continued reference to FIG. 4, at a third step 106, a processordetermines, based on the first timestamp, that the first data fallswithin the overlap region 36. This may be performed by determiningwhether the first timestamp is associated with a time defined within theoverlap region 36. At a fourth step 108, a processor, upon determiningthat the first data falls within the overlap region 36, may store thefirst data to the first data structure 12 and the second data structure14 (because the overlap region 36 is associated with both the first datastructure 12 and the second data structure 14). If the first data is aduplicate of data previously stored, it may not be subsequently stored(because it is a duplicate). However, if the first data is not aduplicate, it may be further processed (as necessary) prior to, during,or after the first data has been stored.

With continued reference to FIG. 4, at a fifth step 110, a processorreceives second data including a second timestamp and a second data ID.The second data may be the same or different from the first data (e.g.,duplicate data or different data). The second data may be received fromthe same or a different source (e.g., requesting device 42) as the firstdata.

With continued reference to FIG. 4, at a sixth step 112, a processor maydetermine that the second data falls within the overlap time interval.At a seventh step 116, a processor may determine that the first data andthe second data are duplicates of one another. This may be at leastpartially based on the second data ID matching the stored (in the datastructure) first data ID. The data IDs of two data entries may indicatethat the request to process the data is a duplicate and that the systemhas already processed that particular data.

Determining that the first data and the second data are duplicates ofone another may be determined by the first data structure 12 and/or thesecond data structure 14. This may include the request processor 44communicating to the first data structure 12 and/or the second datastructure 14 to write the second data to the data structure and thefirst and/or second data structure 12, 14 determining that the seconddata is duplicate data to the first data. The first and/or second datastructure 12, 14 in this case may communicate to the request processor44 that the second data has not been stored because it is duplicatedata. For example, the first and/or second data structure 12, 14 mayreturn a value indicating that the entry is duplicative. As an example,in response to an operation to insert the second data into the firstdata structure and/or the second data structure 12, 14, the datastructure(s) may return a value indicating that the second data is aduplicate. The return may be provided by the programmatic functionalityof the data structure(s) itself, and may be binary to indicate whetherthe insertion operation succeeded or failed. A failed return in such anexample indicates that there is a duplicate.

In some examples, determining that the first data and the second dataare duplicates of one another may be determined by the request processor44 querying the first and/or the second data structures 12, 14associated with the overlap time interval. In some examples, the requestprocessor 44 may query only the relevant data structure (a relevant datastructure being a data structure that is associated with the overlaptime interval) that includes data temporally later than the latest datain the temporally preceding data structure having the overlap timeinterval.

Upon determining that the second data is a duplicate of the first data,the request processor 44 may initiate at least one suitable response. Inone example, the request processor 44 terminates processing of thesecond data because the second data is a duplicate of the first data,which has already been processed. Thus, the system may save processingtime and increase efficiency by not processing (terminating processing)the second data.

In another example, upon determining that the second data is duplicateof the first data, the request processor 44 may generate and communicatea duplicate response message to the requesting device 42. The duplicateresponse message may include data that identifies the second data asidentical to the first data. The duplicate response message may indicatethat the second data was not processed because it was previouslyprocessed as the first data. The duplicate response message may beidentical to the response message sent to the requesting device 42 afterprocessing the first data.

In another example, upon determining that the second data is duplicateof the first data, the system may forgo querying remaining datastructures (data structures other than first data structure 12 and/orthe second data structure). Since the first data structure 12 and/or thesecond data structure was queried, the remaining data structures are notbe queried because the system of the present invention ensures that thedata would have been stored in the first data structure 12 and/or thesecond data structure. This feature reduces overall querying time andefficiency of the computer system.

A computer program product is also contemplated for preventingduplication of data processing, the computer program product includingat least one non-transitory computer-readable medium including programinstructions that, when executed by at least one computer including atleast one processor, causes the at least one processor to effect themethod steps as outlined in FIG. 4 and described above.

While the present invention has been described thus far as preventingduplication of data processing, it will be appreciated that the data canbe data associated with any number of activities, including, but notlimited to, data associated with payment transactions, tokens issued fortemporary use in connection with a payment transaction, a passwordissued for temporary use in connection with a user account, an offerissued for temporary use redeemable with a payment transaction, and thelike. Specific implementations of the present invention for theserelevant types of data is hereinafter described.

Processing of Payment Transactions

Non-limiting embodiments or aspects of the present invention aredirected to a method, system and computer program product for preventingduplicate processing of a payment transaction. The advantages of thisnon-limiting embodiment or aspect include the previously-describedadvantages of the method, system, and computer program product forpreventing duplication of data processing. The present invention ensuresthat duplicate transaction processing request messages are identifiedsuch that payment transactions that have already been processed are notre-processed. This allows the system to be less error prone such thatthe computer system (or other computer systems) are not later requiredto correct mistakes associated with processing a payment transactionmultiple times (such as transfer money back to the original accounts).The present invention also allows for detection of potentiallyfraudulent transaction processing request messages that arecommunicating a duplicate payment transaction to the computer system forprocessing in order to fraudulently obtain funds resulting fromduplicate processing of the payment transaction. Upon detection ofpotentially fraudulent activity, protocols can be initiated to preventthe fraudulent activity or detect its source.

Referring to FIG. 5, a method 120 for preventing duplicate processing ofa payment transaction is shown. At a first step 122, a processorgenerates a plurality of data structures 52 (including the first datastructure 12 and the second data structure 14). The first data structure12 and the second data structure 14 are as previously described andinclude the overlap region 36. The first step 122 is identical to thefirst step 102 from the method 100 described in FIG. 4 except the datain the method 120 is specifically associated with a payment transactionbetween a user and a merchant initiated using a portable financialdevice.

Referring to FIG. 6, the first data structure 12 (and all other datastructures included therewith) is shown. The first data structure 12 maystore the data associated with payment transactions (transaction data).The transaction data may include a PAN number 146 (or other accountidentifier), a transaction ID 148, and a timestamp 150. The transactionID 148 may be a unique identifier that allows the payment transaction tobe identified solely based on that transaction ID 148. The transactionID 148 may take any form, as previously discussed in connection with thefirst data ID. The timestamp 150 may associate the payment transactionwith a specific time, such as the time the payment transaction wasinitiated. However, the timestamp 150 may be assigned based on otherevents occurring during processing of the payment transaction, such aswhen the payment transaction was received by a certain party/system(e.g., merchant system, transaction service provider, issuer, and thelike), when the transaction ID was generated for association with aparticular payment transaction, when the payment transaction wastransmitted from one party/system to another party/system, and the like.Other transaction data may be included in the data structure, such as:cardholder information (e.g., name, contact information, demographics,etc.), merchant information (e.g., merchant name, merchant ID, merchantbank identification number (BIN), etc.), information about thegoods/services purchased (e.g., type of goods, quantity of goods, priceof goods, UPC code, etc.), information about the portable financialdevice (e.g., expiration data, cvv code, spend limit, etc.), and otherinformation that may be included for processing transactions initiatedusing a portable financial device (e.g., ISO defined data elementsaccording to ISO 8583).

Referring back to FIG. 1 the predetermined time intervals (T₁, T₂, andT₃) may be the same or different in length and may be of any lengthappropriate for storage of transaction data. In one example, thepredetermined time intervals may include at least one month, such as atleast two months, one quarter, six months, or twelve months. In oneexample, the predetermine time interval is approximately one month, andall payment transactions initiated during a calendar month (plus theoverlap region 36) are associated with the predetermined time interval.The overlap regions 36 may be the same or different and may be anyoverlap length appropriate for capturing payment transactions that mayhave been delayed in their initiation and/or storage due to computersystem malfunction. The overlap region 36 may be shorter than thepredetermined time intervals. The overlap region may range from 1 minutein length to 1 day in length, such as 1 or 2 hours.

Referring back to FIG. 5, the method 120 may further include a secondstep 124 of receiving first transaction data. The first transaction datamay include any of the previously described transaction data, such as afirst PAN number, a first transaction ID, and/or a first timestamp. At athird step 126, a processor determines, based on the first timestamp,that the first transaction data falls within the overlap region 36. Thismay be performed by determining whether the first timestamp isassociated with a time defined within the overlap region 36. At a fourthstep 128, a processor, upon determining that the first transaction datafalls within the overlap region 36, may store the first transaction datato the first data structure 12 and the second data structure 14 (becausethe overlap region 36 is associated with both the first data structure12 and the second data structure 14). If the first transaction data is aduplicate of transaction data previously stored, it may not besubsequently stored (because it is a duplicate). However, if the firsttransaction data is not a duplicate, it may be further processed priorto, during, or after the first transaction data has been stored. Furtherprocessing may include authorization, clearing, and settling of thepayment transaction.

With continued reference to FIG. 5, at a fifth step 130, a processorreceives second transaction data including a second PAN number, a secondtimestamp, and/or a second transaction ID. The second transaction datamay be the same or different from the first transaction data (e.g.,duplicate data or different data). The second transaction data may bereceived from the same or a different source (e.g., requesting device42) as the first transaction data. For example, the first transactiondata and the second transaction data may be received by the requestprocessor 44 from a merchant system, with the second payment transactionbeing received based on the merchant system malfunctioning andinadvertently (not fraudulently) re-submitting the first transactiondata as second transaction data. In another non-limiting example, thefirst transaction data may be received from the merchant system, and thesecond transaction data may be received by a fraudulent system(different from the initial merchant system) intending to receive fundsby the request processor 44 not determining that the first transactiondata and second transaction data are identical and re-processing thesecond transaction data.

With continued reference to FIG. 5, at a sixth step 132, a processor maydetermine that the second transaction data falls within the overlap timeinterval. At a seventh step 136, a processor may determine that thefirst transaction data and the second transaction data are duplicates ofone another. This may be at least partially based on the secondtransaction ID matching the stored (in the data structure) firsttransaction ID. The transaction IDs of two data entries may indicatethat the request to process the transaction data is a duplicate and thatthe system has already processed that particular transaction data.

Determining that the first transaction data and the second transactiondata are duplicates of one another may be determined by the first datastructure 12 and/or the second data structure 14. This may include therequest processor 44 communicating to the first data structure 12 and/orthe second data structure 14 to write the second transaction data to thedata structure and the first and/or second data structure 12, 14determining that the second transaction data is duplicate to the firsttransaction data. The first and/or second data structure 12, 14 in thiscase may communicate to the request processor 44 that the secondtransaction data has not been stored because it is a duplicate paymenttransaction. For example, the first and/or second data structure 12, 14may return a value indicating that the entry is duplicative. As anexample, in response to an operation to insert the second transactiondata into the first data structure and/or the second data structure 12,14, the data structure(s) may return a value indicating that the secondtransaction data is a duplicate. The return may be provided by theprogrammatic functionality of the data structure(s) itself, and may bebinary to indicate whether the insertion operation succeeded or failed.A failed return in such an example indicates that there is a duplicate.

In some examples, determining that the first transaction data and thesecond transaction data are duplicates of one another may be determinedby the request processor 44 querying the first and/or the second datastructures 12, 14 associated with the overlap time interval. In someexamples, the request processor 44 may query only the relevant datastructure that includes transaction data temporally later than thelatest transaction data in the temporally preceding data structurehaving the overlap time interval.

Upon determining that the second transaction data is a duplicate of thefirst transaction data, the request processor 44 may initiate a suitableresponse, as follows.

With continued reference to FIG. 5, at a step 8 a 138, the requestprocessor 44 may terminate processing of the second payment transaction.This may include the second payment transaction not being authorized,cleared, and settled. At a step 8 b 140, the request processor 44 maygenerate and communicate a duplicate transaction response message to therequesting device 42. The duplicate transaction response message mayinclude data that identifies the second transaction data as identical tothe first transaction data. The duplicate transaction response messagemay indicate that the second transaction data was not processed becauseit was previously processed as the first transaction data. The duplicatetransaction response message may be identical to the transactionresponse message sent to the requesting device 42 after processing thefirst transaction data.

At a step 8 c 142, upon determining that the second transaction data isduplicate of the first transaction data, the system may forgo queryingremaining data structures (data structures other than first datastructure 12 and/or the second data structure). Since the first datastructure 12 and/or the second data structure was queried, the remainingdata structures are not be queried because the system of the presentinvention ensures that the transaction data would have been stored inthe first data structure 12 and/or the second data structure. Thisfeature reduces overall querying time and efficiency of the computersystem.

At a step 8 d 144 the request processor 44 may initiate a fraudulenttransaction submission protocol. This protocol may initiate at least onestep that allows the submission of the second transaction data to bereviewed for potential fraud. This may include transmitting a message tothe transaction service provider and/or the issuer of the portablefinancial device associated with the second transaction data thatnotifies of this potential fraud. The request processor 44 may alsonotify the cardholder of potential fraud by communicating with thecardholder, such as by email, phone call, text message, or othercommunication means. The request processor 44 may temporally halt anyfurther transaction activity associated with the portable financialdevice associated with the second transaction data until the potentialfraud is investigated.

Each of these potential steps 138-144 initiated by the request processor44 may enhance the overall efficiency of the computer system and thesecurity associated with each cardholder account.

Referring to FIG. 7A, a system 160 for preventing duplicate processingof a payment transaction, the system 160 processing a first request forprocessing the payment transaction, is shown. The system 160 may includea merchant system 162 operated by or on behalf of a merchant engaging inpayment transactions with users (cardholders). The merchant system 162may be a merchant POS system. The merchant system 162 may include thefeatures of the previously described requesting device 42.

The merchant system 162 may be in communication with a transactionprocessing server 166 operated by or on behalf of a transaction serviceprovider. The merchant system 162 may transmit transaction processingrequests including transaction data to the transaction processing server166 to request processing of payment transactions. The transactionprocessing server 166 may include the features of the previouslydescribed request processor 44. The transaction processing server 166may be in communication with an issuer server 168 operated by or onbehalf of an issuer of a portable financial device (issued to the user).The merchant system 162, transaction processing server 166, and issuerserver 168 may be in communication with one another to process paymenttransactions, such as to authorize, clear, and settle the paymenttransactions.

With continued reference to FIG. 7A, the system 160 may further includeat least one server 62, as previously described (the example in FIG. 7Aincludes a single server, but it will be appreciated that multipleservers 46, 48, 50 may be included). In the non-limiting example shownin FIG. 7A, the server 62 is in communication with the transactionprocessing server 166; however, it will be appreciated that the servermay instead or in addition be in communication with the issuer server168. The server 62 may be operated by or on behalf of the transactionservice provider and/or the issuer. The server 62 includes datastructures 52 including the first data structure 12 and the second datastructure 14. In some examples, the system 160 may include multipleservers, and the first data structure 12 and the second data structure14 may be stored on separate servers.

With continued reference to FIG. 7A, the merchant system 162 maycommunicate a first transaction processing request including a requestto process a first payment transaction including first transaction datato the transaction processing server 166. The transaction processingserver 166 may execute the method 120 described in FIG. 5 and determinethat the first transaction data is not duplicate transaction data andhas not been processed. The transaction processing server 166 may thencommunicate with the issuer server 168 to process the first paymenttransaction. The issuer server 168 may determine whether the firstpayment transaction should be authorized (approved or declined) andcommunicate its authorization decision to the transaction processingserver 166. The transaction processing server 166 may communicate afirst transaction response message to the merchant system 162 whichcommunicates that the first payment transaction has beenapproved/declined and/or the that the first transaction data has beenprocessed.

Referring to FIG. 7B, the merchant system 162 may communicate a secondtransaction processing request including a request to process a secondpayment transaction including second transaction data to the transactionprocessing server 166. The second payment transaction (and secondtransaction data thereof) and first payment transaction (and firsttransaction data thereof) are identical in this example. The transactionprocessing server 166 may execute the method 120 described in FIG. 5 anddetermine that the second transaction data is a duplicate of the firsttransaction data. The transaction processing server 166 may thencommunicate a second transaction response message to the merchant system162 to communicate that the request to process the second paymenttransaction is denied and may indicate that the second transaction datais a duplicate of the first transaction data, which was alreadyprocessed. The transaction processing server 166 or other components ofthe system 170 may initiate further action as described in connectionwith the steps 9 a-9 d in the method 120 of FIG. 5. In some non-limitingexamples, the merchant system 162 in FIG. 7B is the same as the merchantsystem 162 in FIG. 7A, and the merchant system 162 may haveinadvertently (not fraudulently) resent the second transaction data tothe transaction processing server 166, for instance, because of themerchant system 162 malfunctioning. However, in other non-limitingembodiments, the merchant system 172 from FIG. 7A may be replaced with afraudulent system 172 in FIG. 7B, which is a system operated by or onbehalf of an individual or entity intending to perpetrate a fraud (byreceiving funds from re-processing the second transaction data). Thus,the system 170 may prevent inadvertent duplicate transaction processingrequests or malevolent (fraudulent) duplicate transaction processingrequests.

A computer program product is also contemplated for preventing duplicateprocessing of a payment transaction, the computer program productincluding at least one non-transitory computer-readable medium includingprogram instructions that, when executed by at least one computerincluding at least one processor, causes the at least one processor toeffect the method steps as outlined in FIG. 5, and systems 160, 170 fromFIGS. 7A-7B, and described above.

Processing of Temporary Tokens

Non-limiting embodiments or aspects of the present invention aredirected to a method, system and computer program product for preventingduplicate processing of a token issued for temporary use. The advantagesof this non-limiting embodiment or aspect include thepreviously-described advantages of the method, system, and computerprogram product for preventing duplication of data processing. Thepresent invention ensures that duplicate token processing requestmessages are identified such that tokenized transactions that havealready been processed are not re-processed. This allows the system tobe less error prone such that the computer system (or other computersystems) are not later required to correct mistakes associated withprocessing a tokenized transaction multiple times (such as transfermoney back to the original accounts). The present invention also allowsfor detection of potentially fraudulent token processing requestmessages that are communicating a duplicate tokenized transaction to thecomputer system for processing in order to obtain funds resulting fromduplicate processing of the tokenized transaction. Upon detection ofpotentially fraudulent activity, protocols can be initiated to preventthe fraudulent activity or detect its source.

Referring to FIG. 8, a method 180 for preventing duplicate processing ofa token assigned for temporary use is shown. The token may be asubstitute account identifier for a PAN number to initiate and/orprocess a payment transaction, and the token may have an expirationdate, such that it is no longer valid for initiating and/or processing apayment transaction after its expiration. The token may be associatedwith a PAN number or be generated for use with a single transactionassociated with the PAN number.

At a first step 182, a processor generates a plurality of datastructures 52 (including the first data structure 12 and the second datastructure 14). The first data structure 12 and the second data structure14 are as previously described and include the overlap region 36. Thefirst step 182 is identical to the first step 102 from the method 100described in FIG. 4 except the data in the method 120 is specificallyassociated with a tokenized payment transaction using a token assignedfor temporary use.

Referring to FIG. 9, the first data structure 12 (and all other datastructures included therewith) is shown. The first data structure 12 maystore the data associated with token. The token data may include a PANnumber 146 (or other account identifier), a token ID 206, and atimestamp 208. The token ID 206 may be a unique identifier that allowsthe tokenized transaction to be identified solely based on that token ID206. The token ID 206 may take any form, as previously discussed inconnection with the first data ID. The timestamp 208 may associate thetokenized transaction with a specific time, such as the time thetokenized transaction was initiated and/or the token generated andassigned. However, the timestamp 208 may be assigned based on otherevents occurring during processing of the tokenized transaction, such aswhen the tokenized transaction was received by a certain party (e.g.,merchant system, transaction service provider, issuer, and the like)when the tokenized transaction was transmitted from one party to anotherparty, and the like. Other token data may be included in the datastructure, such as: cardholder information of the user in the tokenizedtransaction (e.g., name, contact information, demographics, etc.),merchant information of the merchant in the tokenized transaction (e.g.,merchant name, merchant ID, merchant bank identification number (BIN),etc.), information about the goods/services purchased in the tokenizedtransaction (e.g., type of goods, quantity of goods, price of goods, UPCcode, etc.), information about the portable financial device associatedwith the token (e.g., expiration data, cvv code, spend limit, etc.), andother information that may be included for processing tokenizedtransactions initiated using a portable financial device (e.g., ISOdefined data elements according to ISO 8583).

Referring back to FIG. 1 the predetermined time intervals (T₁, T₂, andT₃) may be the same or different in length and may be of any lengthappropriate for storage of a temporary token. In one example, thepredetermined time intervals may include at least one month, such as atleast two months, one quarter, six months, or twelve months. In oneexample, the predetermine time interval is approximately one month, andall tokens assigned during a calendar month (plus the overlap region 36)are associated with the predetermined time interval. The overlap regions36 may be the same or different and may be any overlap lengthappropriate for capturing assignment of temporary tokens that may bebeen delayed in their generation and/or storage due to computer systemmalfunction. The overlap region 36 may be shorter than the predeterminedtime intervals. The overlap region may range from 1 minute in length to1 day in length, such as 1 hour.

Referring back to FIG. 8, the method 180 may further include a secondstep 184 of receiving first token data. A processor may determinewhether the first token associated with the first token data is anexpired token. The first token data may include any of the previouslydescribed token data, such as a first PAN number, a first token ID,and/or a first timestamp. At a third step 186, a processor determinesbased on the first timestamp that the first token data falls within theoverlap region 36. This may be performed by determining whether thefirst timestamp is associated with a time defined within the overlapregion 36. At a fourth step 188, a processor, upon determining that thefirst token data falls within the overlap region 36, may store the firsttoken data to the first data structure 12 and the second data structure14 (because the overlap region 36 is associated with both the first datastructure 12 and the second data structure 14). If the first token datais a duplicate of token data previously stored, it may not besubsequently stored (because it is a duplicate). However, if the firsttoken data is not a duplicate, it may be processed prior to, during, orafter the first token data has been stored, such as authorization,clearing, and settling of the tokenized transaction.

With continued reference to FIG. 8, at a fifth step 190, a processorreceives second token data including a second PAN number, a secondtimestamp and/or a second token ID. A processor may determine whetherthe second token associated with the second token data is an expiredtoken. The second token data may be the same or different from the firsttoken data (e.g., duplicate data or different data). The second tokendata may be received from the same or a different source (e.g.,requesting device 42) as the first token data. For example, the firsttoken data and the second token data may be received by the requestprocessor 44 from a merchant system, with the second tokenizedtransaction being received based on the merchant system malfunctioningand inadvertently re-submitting the first token data as second tokendata. In another non-limiting example, the first token data may bereceived from the merchant system, and the second token data may bereceived by a separate fraudulent system intending to receive funds bythe request processor 44 not determining that the first token data andsecond token data are identical and re-processing the second token data.

With continued reference to FIG. 8, at a sixth step 192, a processor maydetermine that the second token data falls within the overlap timeinterval. At a seventh step 196, a processor may determine that thefirst token data and the second token data are duplicates of oneanother. This may be at least partially based on the second token IDmatching the stored (in the data structure) first token ID. The tokenIDs of two data entries may indicate that the request to process thetoken data is a duplicate and that the system has already processed thatparticular token data.

Determining that the first token data and the second token data areduplicates of one another may be determined by the first data structure12 and/or the second data structure 14. This may include the requestprocessor 44 communicating to the first data structure 12 and/or thesecond data structure 14 to write the second token data to the datastructure and the first and/or second data structure 12, 14 determiningthat the second token data is duplicate to the first token data. Thefirst and/or second data structure 12, 14 in this case may communicateto the request processor 44 that the second token data has not beenstored because it is a duplicate token. For example, the first and/orsecond data structure 12, 14 may return a value indicating that theentry is duplicative. As an example, in response to an operation toinsert the second token data into the first data structure and/or thesecond data structure 12, 14, the data structure(s) may return a valueindicating that the second token data is a duplicate. The return may beprovided by the programmatic functionality of the data structure(s)itself, and may be binary to indicate whether the insertion operationsucceeded or failed. A failed return in such an example indicates thatthere is a duplicate.

In some examples, determining that the first token data and the secondtoken data are duplicates of one another may be determined by therequest processor 44 querying the first and/or the second datastructures 12, 14 associated with the overlap time interval. In someexamples, the request processor 44 may query only the relevant datastructure that includes token data temporally later than the latesttoken data in the temporally preceding data structure having the overlaptime interval.

Upon determining that the second token data is a duplicate of the firsttoken data, the request processor 44 may initiate a suitable response,as follows.

With continued reference to FIG. 8, at a step 8 a 198, the requestprocessor 44 may terminate processing of the second tokenizedtransaction. This may include the second tokenized transaction not beingauthorized cleared, and settled. At a step 8 b 200, the requestprocessor 44 may generate and communicate a duplicate token responsemessage to the requesting device 42. The duplicate token responsemessage may include data that identifies the second token data asidentical to the first token data. The duplicate token response messagemay indicate that the second token data was not processed because it waspreviously processed as the first token data. The duplicate tokenresponse message may be identical to the token response message sent tothe requesting device 42 after processing the first token data.

At a step 8 c 202, upon determining that the second token data isduplicate of the first token data, the system may forgo queryingremaining data structures (data structures other than first datastructure 12 and/or the second data structure). Since the first datastructure 12 and/or the second data structure was queried, the remainingdata structures are not be queried because the system of the presentinvention ensures that the token data would have been stored in thefirst data structure 12 and/or the second data structure. This featurereduces overall querying time and efficiency of the computer system.

At a step 8 d 204 the request processor 44 may initiate a fraudulenttoken submission protocol. This protocol may initiate at least one stepthat allows the submission of the second token data to be reviewed forpotential fraud. This may include transmitting a message to thetransaction service provider and/or the issuer of the token associatedwith the second token data that notifies of this potential fraud. Therequest processor 44 may also notify the cardholder (associated with thetoken) of potential fraud by communicating with the cardholder, such asby email, phone call, text message, or other communication means. Therequest processor 44 may temporally halt any further transactionactivity associated with the portable financial device associated withthe second token data until the potential fraud is investigated.

Each of these potential steps 198-204 initiated by the request processor44 may enhance the overall efficiency of the computer system and thesecurity associated with each cardholder account.

Referring to FIG. 10A, the system 210 is identical to the system 160from FIG. 7A except in the following ways. The merchant system 162 inFIG. 10A may communicate a first tokenized processing request includinga request to processes a first tokenized transaction including firsttoken data to the transaction processing server 166. The transactionprocessing server 166 may execute the method 180 described in FIG. 8 anddetermine that the first token data is not duplicate data and has notbeen processed. The transaction processing server 166 may thencommunicate with the issuer server 168 to process the first tokenizedtransaction. The issuer server 168 may determine whether the firsttokenized transaction should be authorized (approved or denied) andsubmit its authorization decision to the transaction processing server166. The transaction processing server 166 may communicate a firsttokenized response message to the merchant system 162 which communicatesthat the first tokenized transaction has been approved and/or the thatthe first tokenized data has been processed.

Referring to FIG. 10B, the system 212 is identical to the system 170from FIG. 7B except in the following ways. The merchant system 162 orfraudulent system 172 may communicate a second tokenized processingrequest including a request to process a second tokenized transactionincluding second token data to the transaction processing server 166.The second tokenized transaction (and second token data thereof) andfirst tokenized transaction (and first token data thereof) are identicalin this example. The transaction processing server 166 may execute themethod 180 described in FIG. 8 and determine that the second token datais a duplicate of the first token data. The transaction processingserver 166 may then communicate a second tokenized response message tothe merchant system 162 or fraudulent system 172 to communicate that therequest to process the second tokenized transaction is denied and mayindicate that the second token data is a duplicate of the first tokendata, which was already processed.

A computer program product is also contemplated for preventing duplicateprocessing of a token issued for temporary use, the computer programproduct including at least one non-transitory computer-readable mediumincluding program instructions that, when executed by at least onecomputer including at least one processor, causes the at least oneprocessor to effect the method steps as outlined in FIG. 8, and systems210, 212 from FIGS. 10A-10B, and described above.

Processing of Temporary Passwords

Non-limiting embodiments or aspects of the present invention aredirected to a method, system and computer program product for preventingduplicate processing of a password issued for temporary use. Theadvantages of this non-limiting embodiment or aspect include thepreviously-described advantages of the method, system, and computerprogram product for preventing duplication of data processing. Thepresent invention ensures that duplicate password processing requestmessages are identified such that the password cannot be used more thana single time to login to a user account. This allows the system to beless error prone and allows the user account to be more secure. Thepresent invention also allows for detection of potentially fraudulentpassword processing request messages, such as subsequent login attemptsusing the temporary password by an identity thief. Upon detection ofpotentially fraudulent activity, protocols can be initiated to preventthe fraudulent activity or detect its source.

Referring to FIG. 11, a method 220 for preventing duplicate processingof a password assigned for temporary use is shown. At a first step 222,a processor generates a plurality of data structures 52 (including thefirst data structure 12 and the second data structure 14). The firstdata structure 12 and the second data structure 14 are as previouslydescribed and include the overlap region 36. The first step 222 isidentical to the first step 102 from the method 100 described in FIG. 4except the data in the method 220 is specifically associated with apassword of a user account assigned for temporary use. A passwordassigned for temporary use may be the initial password associated withan account, which the user may use at the first login, and thistemporary password may be replaced with a user chosen password. Apassword assigned for temporary use may be a password associated with auser account in response to a user forgetting their current password,which the user may use at the next login, and this temporary passwordmay be replaced with a new user chosen password. This password mayexpire after a certain period of time, at which time a new temporarypassword may be required to login to the user account. For example, thetemporary password may only be valid for several hours, days, weeks, ormonths. As used herein, “password” may refer to any sequence of number,letters, or symbols which may be entered to allow a user to access theirpassword-secured account.

Referring to FIG. 12, the first data structure 12 (and all other datastructures included therewith) is shown. The first data structure 12 maystore the data associated with a temporary password issued in connectionwith a user account (password data). The password data may include ausername 246 associated with the user account, a temporary password 248,and a timestamp 250. The temporary password 248 may be a unique passwordthat allows a user to access the user account when entered into a loginscreen. The timestamp 150 may associate the temporary password with aspecific time, such as the time the temporary password was issued.However, the timestamp 150 may be assigned based on other eventsoccurring during processing of the password, such as an initial logintime, the time of the request for issuance of a temporary password, thetime the account associated with the temporary password was initiated,and the like. Other transaction data may be included in the datastructure, such as user information (e.g., name, contact information,demographics, etc.) or an account identifier associated with the useraccount.

Referring back to FIG. 1 the predetermined time intervals (T₁, T₂, andT₃) may be the same or different in length and may be of any lengthappropriate for storage of password data. In one example, thepredetermined time intervals may include at least one month, such as atleast two months, one quarter, six months, or twelve months. In oneexample, the predetermine time interval is approximately one month, andall temporary passwords issued during a calendar month (plus the overlapregion 36) are associated with the predetermined time interval. Theoverlap regions 36 may be the same or different and may be any overlaplength appropriate for capturing password data that may be been delayedin its issuance and/or storage due to computer system malfunction. Theoverlap region 36 may be shorter than the predetermined time intervals.The overlap region may range from 1 minute in length to 1 day in length,such as 1 hour.

Referring back to FIG. 11, the method 220 may further include a secondstep 224 of receiving first password data. A processor may determinewhether the first password associated with the first password data is anexpired password. Receiving first password data may refer to a loginattempt (a password processing request message) in which a user entersin a temporary password, such that the temporary password can beassociated with the corresponding username and/or timestamp. The firstpassword data may include any of the previously described password data,such as a first username, a first temporary password, and/or a firsttimestamp. At a third step 226, a processor determines based on thefirst timestamp that the first password data falls within the overlapregion 36. This may be performed by determining whether the firsttimestamp is associated with a time defined within the overlap region36. At a fourth step 228, a processor, upon determining that the firstpassword data falls within the overlap region 36, may store the firstpassword data to the first data structure 12 and the second datastructure 14 (because the overlap region 36 is associated with both thefirst data structure 12 and the second data structure 14). If the firstpassword data is a duplicate of password data previously stored, it maynot be subsequently stored (because it is a duplicate). However, if thefirst password data is not a duplicate, it may be processed prior to,during, or after the first password data has been stored by allowing theuser access to the account upon entering the temporary password.

With continued reference to FIG. 11, at a fifth step 230, a processorreceives second password data including a second username, a secondtimestamp and/or a second temporary password. A processor may determinewhether the second temporary password associated with the secondpassword data is an expired password. The second password data may bethe same or different from the first password data (e.g., duplicate dataor different data).

With continued reference to FIG. 11, at a sixth step 232, a processormay determine that the second password data falls within the overlaptime interval. At a seventh step 236, a processor may determine that thefirst password data and the second password data are duplicates of oneanother. This may be at least partially based on the second password IDmatching the stored (in the data structure) first password ID. Thepassword IDs of two data entries may indicate that the request toprocess the password data is a duplicate and that the system has alreadyprocessed that particular password data.

Determining that the first password data and the second password dataare duplicates of one another may be determined by the first datastructure 12 and/or the second data structure 14. This may include therequest processor 44 communicating to the first data structure 12 and/orthe second data structure 14 to write the second password data to thedata structure and the first and/or second data structure 12, 14determining that the second password data is duplicate to the firstpassword data. The first and/or second data structure 12, 14 in thiscase may communicate to the request processor 44 that the secondpassword data has not been stored because it is a duplicate password.For example, the first and/or second data structure 12, 14 may return avalue indicating that the entry is duplicative. As an example, inresponse to an operation to insert the second password data into thefirst data structure and/or the second data structure 12, 14, the datastructure(s) may return a value indicating that the second password datais a duplicate. The return may be provided by the programmaticfunctionality of the data structure(s) itself, and may be binary toindicate whether the insertion operation succeeded or failed. A failedreturn in such an example indicates that there is a duplicate.

In some examples, determining that the first password data and thesecond password data are duplicates of one another may be determined bythe request processor 44 querying the first and/or the second datastructures 12, 14 associated with the overlap time interval. In someexamples, the request processor 44 may query only the relevant datastructure that includes password data temporally later than the latestpassword data in the temporally preceding data structure having theoverlap time interval.

Upon determining that the second password data is a duplicate of thefirst password data, the request processor 44 may initiate a suitableresponse, as follows.

With continued reference to FIG. 11, at a step 8 a 238, the requestprocessor 44 may terminate processing of the second password entry(e.g., deny entry of access to a user account upon the second use of thetemporary password). At a step 8 b 240, the request processor 44 maygenerate and communicate a duplicate password response message to therequesting device 42. The duplicate password response message mayinclude data that identifies the second password data as identical tothe first password data. The duplicate password response message mayindicate that the second password data was not processed because it waspreviously processed as the first password data.

At a step 8 c 242, upon determining that the second password data isduplicate of the first password data, the system may forgo queryingremaining data structures (data structures other than first datastructure 12 and/or the second data structure). Since the first datastructure 12 and/or the second data structure was queried, the remainingdata structures are not be queried because the system of the presentinvention ensures that the password data would have been stored in thefirst data structure 12 and/or the second data structure. This featurereduces overall querying time and efficiency of the computer system.

At a step 8 d 244 the request processor 44 may initiate a fraudulentpassword submission protocol. This protocol may initiate at least onestep that allows the submission of the second password data to bereviewed for potential fraud. This may include transmitting a message tothe issuer of the user account that notifies of this potential fraud.The request processor 44 may also notify the user of potential fraud bycommunicating with the user, such as by email, phone call, text message,or other communication means. The request processor 44 may temporallyhalt any further access of user to the user account until the potentialfraud is investigated.

Each of these potential steps 238-244 initiated by the request processor44 may enhance the overall efficiency of the computer system and thesecurity associated with each cardholder account.

Referring to FIG. 13A, a login screen for processing of a passwordassigned for temporary use, the system processing a first request forprocessing the password, is shown. The login screen may include a userinterface and fields into which the user enters password data. The usermay enter the temporary password into a freeform field. The user mayalso enter a username associated with the temporary password into afreeform field. There may be other freeform fields or other fields thata user may fill in to login to the user account. Upon entering thetemporary password, the timestamp and other of the first password dataassociated therewith may be retrieved by the system. The requestprocessor 44 may use this first password data to execute the method 220described in FIG. 11 and determine that the first password data is notduplicate data and has not been used to access the user account. Theuser may then be allowed access to the user account based on enteringthe correct temporary password. The user interface may indicate that thelogin attempt using the temporary password was successful.

Referring to FIG. 13B, a login screen for preventing duplicateprocessing of a password assigned for temporary use, the systemprocessing a second duplicate request for processing the password, isshown. The second password data (and second temporary password thereof)is identical to the first password data (and first temporary passwordthereof). The request processor may use this second password data toexecute the method 220 described in FIG. 11 and determine that thesecond password data is a duplicate of the first password data. The usermay be denied access to the user account based on entering the temporarypassword which has already been used as the first temporary password.The user interface may indicate that the login attempt using thetemporary password failed. Thus, the system may allow access to a useraccount upon entering the correct temporary password a first time, butmay deny access upon the temporary password being used a second time,whether it be re-entered in error by the user or fraudulently by apotential identity thief.

A computer program product is also contemplated for preventing duplicateprocessing of a password assigned for temporary use, the computerprogram product including at least one non-transitory computer-readablemedium including program instructions that, when executed by at leastone computer including at least one processor, causes the at least oneprocessor to effect the method steps as outlined in FIG. 11 anddescribed above.

Processing of Temporary Offers

Non-limiting embodiments or aspects of the present invention aredirected to a method, system and computer program product for preventingduplicate processing of an offer issued for temporary use. Theadvantages of this non-limiting embodiment or aspect include thepreviously-described advantages of the method, system, and computerprogram product for preventing duplication of data processing. Thepresent invention ensures that duplicate offer processing requestmessages are identified such that offers that have already been redeemedare not re-processed. This allows the system to be less error prone suchthat the computer system (or other computer systems) are not laterrequired to correct mistakes associated with processing on offermultiple times (such as transfer money back to the original accounts).The present invention also allows for detection of potentiallyfraudulent offer processing request messages that are communicating aduplicate offer transaction to the computer system for processing inorder to obtain funds or goods/services at a lower rate. Upon detectionof potentially fraudulent activity, protocols can be initiated toprevent the fraudulent activity or detect its source.

Referring to FIG. 14, a method 260 for preventing duplicate processingof an offer issued for temporary redemption is shown. At a first step262, a processor generates a plurality of data structures 52 (includingthe first data structure 12 and the second data structure 14). The firstdata structure 12 and the second data structure 14 are as previouslydescribed and include the overlap region 36. The first step 262 isidentical to the first step 102 from the method 100 described in FIG. 4except the data in the method 260 is specifically associated with anoffer issued for temporary use, redeemable during a payment transactioninitiated using a portable financial device. An offer issued fortemporary use may be an offer associated with a user or a plurality ofusers which, once redeemed, bestows a benefit upon the redeeming user.The benefit may be a discount, a free product, or any other type ofbenefit known in the art. The offer may expire after a certain period oftime. For example the offer may only be valid for several hours, days,weeks, or months.

Referring to FIG. 15, the first data structure 12 (and all other datastructures included therewith) is shown. The first data structure 12 maystore the data associated with temporary offers (offer data). The offerdata may include a PAN number 146 (or other account identifier), atemporary offer ID 286, an offer description 288, and/or a timestamp290. The temporary offer ID 286 may be a unique identifier that allowsthe offer to be identified solely based on that temporary offer ID 286.The temporary offer ID 286 may take any form, as previously discussed inconnection with the first data ID. The timestamp 290 may associate thetemporary offer with a specific time, such as the time the temporaryoffer was initiated and issued. However, the timestamp 290 may beassigned based on other events occurring during processing of the offer,such as when the temporary offer was received by a certain party/system(e.g., merchant, transaction service provider, issuer, user, and thelike), and the like. Other offer data may be included in the datastructure, such as: cardholder information of the portable financialdevice used to initiate the payment transaction during which the offerwas redeemed (e.g., name, contact information, demographics, etc.),merchant information (e.g., merchant name, merchant ID, merchant bankidentification number (BIN), etc.), information about the goods/servicespurchased during the transaction in which the offer was redeemed (e.g.,type of goods, quantity of goods, price of goods, UPC code, etc.),information about the portable financial device during the transactionin which the offer was redeemed (e.g., expiration data, cvv code, spendlimit, etc.), and other information that may be included for processingoffers redeemed during a payment transaction using a portable financialdevice (e.g., ISO defined data elements according to ISO 8583).

Referring back to FIG. 1 the predetermined time intervals (T₁, T₂, andT₃) may be the same or different in length and may be of any lengthappropriate for storage of offer data. In one example, the predeterminedtime intervals may include at least one month, such as at least twomonths, one quarter, six months, or twelve months. In one example, thepredetermine time interval is approximately one month, and all offersissued during a calendar month (plus the overlap region 36) areassociated with the predetermined time interval. The overlap regions 36may be the same or different and may be any overlap length appropriatefor capturing issued offers that may be been delayed in their initiationand/or storage due to computer system malfunction. The overlap region 36may be shorter than the predetermined time intervals. The overlap regionmay range from 1 minute in length to 1 day in length, such as 1 hour.

Referring back to FIG. 14, the method 260 may further include a secondstep 264 of receiving first offer data. A processor may determinewhether the first offer associated with the first offer data is anexpired offer. The first offer data may include any of the previouslydescribed offer data, such as a first PAN number, a temporary offer ID,an offer description and/or a first timestamp. At a third step 266, aprocessor determines based on the first timestamp that the first offerdata falls within the overlap region 36. This may be performed bydetermining whether the first timestamp is associated with a timedefined within the overlap region 36. At a fourth step 268, a processor,upon determining that the first offer data falls within the overlapregion 36, may store the first offer data to the first data structure 12and the second data structure 14 (because the overlap region 36 isassociated with both the first data structure 12 and the second datastructure 14). If the first offer data is a duplicate of transactiondata previously stored, it may not be subsequently stored (because it isa duplicate). However, if the first offer data is not a duplicate, itmay be processed prior to, during, or after the first offer data hasbeen stored, such as application of the benefit of the offer to thepayment transaction with which the offer is redeemed.

With continued reference to FIG. 14, at a fifth step 270, a processorreceives second offer data including a second PAN number, a secondtimestamp, a second offer description, and/or a second offer ID. Aprocessor may determine whether the second offer associated with thesecond offer data is an expired offer. The second offer data may be thesame or different from the first offer data (e.g., duplicate data ordifferent data). The second offer data may be received from the same ora different source (e.g., requesting device 42) as the first offer data.For example, the first offer data and the second offer data may bereceived by the request processor 44 from a merchant system along with apayment transaction processing request, with the second offer data beingreceived based on the merchant system malfunctioning and inadvertentlyre-submitting the first offer data as second offer data. In anothernon-limiting example, the first offer data may be received from themerchant system, and the second offer data may be received by a separatefraudulent system intending to receive funds or a discount by therequest processor 44 not determining that the first offer data andsecond offer data are identical and again applying the second offerdata.

With continued reference to FIG. 14, at a sixth step 272, a processormay determine that the second offer data falls within the overlap timeinterval. At a seventh step 276, a processor may determine that thefirst offer data and the second offer data are duplicates of oneanother. This may be at least partially based on the second offer IDmatching the stored (in the data structure) first offer ID. The offerIDs of two data entries may indicate that the request to process theoffer data is a duplicate and that the system has already processed thatparticular offer data.

Determining that the first offer data and the second offer data areduplicates of one another may be determined by the first data structure12 and/or the second data structure 14. This may include the requestprocessor 44 communicating to the first data structure 12 and/or thesecond data structure 14 to write the second offer data to the datastructure and the first and/or second data structure 12, 14 determiningthat the second offer data is duplicate to the first offer data. Thefirst and/or second data structure 12, 14 in this case may communicateto the request processor 44 that the second offer data has not beenstored because it is a duplicate offer. For example, the first and/orsecond data structure 12, 14 may return a value indicating that theentry is duplicative. As an example, in response to an operation toinsert the second offer data into the first data structure and/or thesecond data structure 12, 14, the data structure(s) may return a valueindicating that the second offer data is a duplicate. The return may beprovided by the programmatic functionality of the data structure(s)itself, and may be binary to indicate whether the insertion operationsucceeded or failed. A failed return in such an example indicates thatthere is a duplicate.

In some examples, determining that the first offer data and the secondoffer data are duplicates of one another may be determined by therequest processor 44 querying the first and/or the second datastructures 12, 14 associated with the overlap time interval. In someexamples, the request processor 44 may query only the relevant datastructure that includes offer data temporally later than the latestoffer data in the temporally preceding data structure having the overlaptime interval.

Upon determining that the second offer data is a duplicate of the firstoffer data, the request processor 44 may initiate a suitable response,as follows.

With continued reference to FIG. 14, at a step 8 a 278, the requestprocessor may 44 terminate processing of the second offer data, suchthat the benefit from the second offer is not redeemed a second time. Ata step 8 b 280, the request processor 44 may generate and communicate aduplicate offer response message to the requesting device 42. Theduplicate offer response message may include data that identifies thesecond offer data as identical to the first offer data. The duplicateoffer response message may indicate that the second offer data was notprocessed because it was previously processed as the first offer data.The duplicate offer response message may be identical to the offerresponse message sent to the requesting device 42 after processing thefirst offer data.

At a step 8 c 282, upon determining that the second offer data isduplicate of the first offer data, the system may forgo queryingremaining data structures (data structures other than first datastructure 12 and/or the second data structure). Since the first datastructure 12 and/or the second data structure was queried, the remainingdata structures are not be queried because the system of the presentinvention ensures that the offer data would have been stored in thefirst data structure 12 and/or the second data structure. This featurereduces overall querying time and efficiency of the computer system.

At a step 8 d 284 the request processor 44 may initiate a fraudulentoffer redemption protocol. This protocol may initiate at least one stepthat allows the submission of the second offer data to be reviewed forpotential fraud. This may include transmitting a message to thetransaction service provider and/or the issuer of the temporary offerassociated with the second offer data that notifies of this potentialfraud.

Each of these potential steps 278-284 initiated by the request processor44 may enhance the overall efficiency of the computer system and ensurethat an offer is not redeemed multiple times.

Referring to FIG. 16A, the system 300 is identical to the system 160from FIG. 7A except in the following ways. The merchant system 162 inFIG. 10A may communicate a first offer processing request including arequest to processes a first offer including first offer data to thetransaction processing server 166. The transaction processing server 166may execute the method 260 described in FIG. 14 and determine that thefirst offer data is not duplicate data and has not been redeemed. Thetransaction processing server 166 may then communicate with the issuerserver 168 to process the first offer (e.g., apply the benefit of theoffer to the payment transaction). The issuer server 168 may determinewhether the payment transaction during which the offer was redeemed andsubmit its authorization decision to the transaction processing server166. The transaction processing server 166 may communicate a first offerresponse message to the merchant system 162 which communicates that thepayment transaction has been approved and redemption of the offer hasbeen approved (redeemed and applied).

Referring to FIG. 16B, the system 310 is identical to the system 170from FIG. 7B except in the following ways. The merchant system 162 orfraudulent system 172 may communicate a second offer processing requestincluding a request to process a second offer including second offerdata to the transaction processing server 166. The second offer (andsecond offer data thereof) and first offer (and first offer datathereof) are identical in this example. The transaction processingserver 166 may execute the method 260 described in FIG. 14 and determinethat the second offer data is a duplicate of the first offer data. Thetransaction processing server 166 may then communicate a second offerresponse message to the merchant system 162 or fraudulent system 172 tocommunicate that the request to process the second offer transaction isdenied and may indicate that the second offer data is a duplicate of thefirst offer data, which was already redeemed.

A computer program product is also contemplated for preventing duplicateprocessing of an offer assigned for temporary use, the computer programproduct including at least one non-transitory computer-readable mediumincluding program instructions that, when executed by at least onecomputer including at least one processor, causes the at least oneprocessor to effect the method steps as outlined in FIG. 14, and systemin FIGS. 16A-16B, and as described above.

EXAMPLE

The following example is provided to illustrate an embodiment of thesystem, method, and computer program product for preventing duplicationof data processing. In this particular example, the data is associatedwith a payment transaction; however, it will be appreciated that otherexamples in which the data is of a different kind are also considered(e.g., token data, password data, offer data, and the like).

Referring to back to FIGS. 2, 4, 5-7 and referring to FIG. 17, a method320 for preventing duplicate processing of a payment transaction isshown. In this Example, Walter Smith is a consumer shopping at Big BoxMart, and Walter purchases a new laptop computer from Big Box Mart. Atthe point-of-sale, Walter presents his portable financial device (creditcard) to the casher to initiate the payment transaction. Big Box Mart'smerchant system (a POS device and a requesting device 42) collectsWalter's credit card information, as well as other relevant transactiondata for completing the payment transaction. The payment transaction wasinitiated on Jan. 31, 2018 at 11:47:23 PM EST. The transaction serviceprovider associated with Walter's credit card is First CC Company, andthe issuer of Walter's Credit Card is First Bank.

At a first step (S1 a-S1 b), a plurality of data structures aregenerated. A first data structure 51 is generated and is stored on afirst server 46, and a separate second data structure 53 is stored on aseparate second server 48. The first server 46 and the second server 48are operated by or on behalf of First CC Company and/or First Bank. Inthis example, the first server 46 and the second server 48 are operatedby or on behalf of First CC Company.

The first data structure 51 and the second data structure 52 storetransaction data associated with payment transactions initiated using aportable financial device. The first data structure 51 is defined by afirst start time of Dec. 31, 2017 at 10:00:00 PM EST and first end timeof Jan. 31, 2018 at 11:59:59 PM EST (T₁). The second data structure 53is defined by a second start time of Jan. 31, 2018 at 10:00:00 PM ESTand a second end time of Feb. 28, 2018 at 11:59:59 PM EST (T₂). Thefirst data structure 31 and second data structure include an overlapregion 36 that overlap with one another (overlap time interval) (Jan.31, 2018 at 10:00:00 PM EST to Jan. 31, 2018 at 11:59:59 PM).

At a second step (S2), Big Box Mart's requesting device 42 communicatesfirst transaction data including the transaction data collected fromWalter associated with the payment transaction for the laptop computer.The first transaction data includes the PAN number associated withWalter's credit card, an assigned unique first transaction ID, and afirst time stamp associated with initiation of the payment transaction.The requesting device 42 communicates the first transaction data to aprocessor operated by or on behalf of First CC Company (a requestprocessor 44). The requesting device 42 and/or the request processor 44associate the first timestamp associated with initiation of the firstpayment transaction and the unique first transaction ID with the paymenttransaction between Walter and Big Box Mart.

At a third step (S3), the request processor 44 determines whether thepayment transaction falls within the overlap region 36 based on thefirst timestamp. Since the transaction was initiated on Jan. 31, 2018 at11:47:23 PM EST, it falls within the overlap region 36. At a fourth step(S4 a-S4 b), the request processor 44 stores the first transaction dataof the payment transaction to the first data structure 51 and the seconddata structure 53. Since this payment transaction has not been processed(the transaction data was not previously stored to the first datastructure 51 and the second data structure 53), the payment transactionis then processed to completion (authorized, cleared, settled).

At some time later, a fraudulent system operated by or on behalf of anidentity thief effects a scheme in which the fraudulent system (now therequesting device 42 for the remaining steps of the process 320)communicates transaction data to the request processor 44 and collectsfunds from the payment transaction being re-processed.

In this example, the fraudulent system obtains the transaction dataassociated with Walter's payment transaction with Big Box Mart for thelaptop computer. This transaction data (referred to hereinafter assecond transaction data) is identical (at least in part) to the firsttransaction data.

At a fifth step (S5), the request processor 44 receives the secondtransaction data from the fraudulent system. The second transaction datahas a second timestamp and a second transaction ID identical to thefirst timestamp and the first transaction id.

At a sixth step (S6), the request processor determines whether thesecond transaction data falls within the overlap region 36. Since thetransaction was initiated on Jan. 31, 2018 at 11:47:23 PM EST, it fallswithin the overlap region 36. At an seventh step (S7), the requestprocessor 44 determines that the second transaction data is a duplicateof the first transaction data (that Walter's payment transaction hasalready been processed). This determination may be made based on theidentical first and second transaction ID.

At a eighth step (S8 a-S8 d), the request processor 44 may initiate anaction in response to determining that the second transaction data is aduplicate of the first transaction data. The request processor 44 mayterminate processing of the second transaction data (S8 a), such thatthe payment transaction is not re-processed. The request processor 44may forgo querying remaining data structures (S8 b). The requestprocessor 44 may initiate a fraudulent transaction submission protocol(S8 c) to determine the identity of the fraudulent system and/or protectWalter's credit card account or Big Box Mart. This may includecommunicating with a device associated with Walter and/or Big Box Martto notify of the potential fraud. The request processor 44 maycommunicate (S8 d) a duplicate transaction data response to thefraudulent system to identifying the payment transaction as havingalready been processed or by returning an identical response compared tothe response sent to Big Box Mart's merchant system upon the firsttransaction data being processed to the fraudulent system.

Although the invention has been described in detail for the purpose ofillustration based on what is currently considered to be the mostpractical and preferred embodiments, it is to be understood that suchdetail is solely for that purpose and that the invention is not limitedto the disclosed embodiments, but, on the contrary, is intended to covermodifications and equivalent arrangements that are within the spirit andscope of the appended claims. For example, it is to be understood thatthe present invention contemplates that, to the extent possible, one ormore features of any embodiment can be combined with one or morefeatures of any other embodiment.

The invention claimed is:
 1. A method for preventing duplicateprocessing of a payment transaction comprising: generating, with atleast one processor, a plurality of data structures, wherein generatingthe plurality of data structures comprises: defining a firstpredetermined time interval comprising a first start time and a firstend time; defining a second predetermined time interval comprising asecond start time and a second end time, wherein the second start timeis after the first start time and before the first end time, and whereinthe second end time is after the first end time; defining an overlaptime interval comprising a third start time and a third end time,wherein the third start time is between the first start time and thefirst end time, wherein the third end time is between the second starttime and the second end time, and wherein the overlap time interval isshorter than a time interval between the first start time and the thirdstart time and a time interval between the third end time and the secondend time; generating a first data structure associated with a firstunique identifier based on the first predetermined time interval,wherein the first data structure stores transaction data associated witha payment transaction that is initiated within the first predeterminedtime interval, the first data structure comprising a first overlapregion corresponding to the overlap time interval; and generating asecond data structure associated with a second unique identifier basedon the second predetermined time interval, wherein the second datastructure stores transaction data associated with a payment transactionthat is initiated within the second predetermined time interval, thesecond data structure comprising a second overlap region correspondingto the overlap time interval; after generating the plurality of datastructures, receiving, with at least one processor, first transactiondata associated with a first payment transaction, wherein the firsttransaction data comprises a first timestamp associated with initiationof the first payment transaction and a first transaction ID;determining, with at least one processor and based on the firsttimestamp, that the first payment transaction falls within the overlaptime interval; upon determining that the first payment transaction fallswithin the overlap time interval storing, with at least one processor,the first transaction data to both the first overlap region of the firstdata structure and the second overlap region of the second datastructure; receiving, with at least one processor, second transactiondata associated with a second payment transaction, wherein the secondtransaction data comprises a second timestamp associated with initiationof the second payment transaction and a second transaction ID;determining, with at least one processor and based on the secondtimestamp, that the second payment transaction falls within the overlaptime interval; upon determining that the second payment transactionfalls within the overlap time interval, determining, with at least oneprocessor and based on matching the first transaction ID to the secondtransaction ID, that the second payment transaction is a duplicate ofthe first payment transaction; and upon determining that the secondpayment transaction is a duplicate of the first payment transaction, atleast one of the following: terminating, with at least one processor,processing of the second payment transaction, and generating, with atleast one processor, a duplicate transaction response.
 2. The method ofclaim 1, further comprising: upon determining that the second paymenttransaction is a duplicate of the first payment transaction,terminating, with at least one processor, processing of the secondpayment transaction.
 3. The method of claim 1, further comprising: upondetermining that the second payment transaction is a duplicate of thefirst payment transaction, generating and communicating, with at leastone processor, a duplicate transaction response, wherein the duplicatetransaction response comprises data associated with identifying thesecond payment transaction as identical to the first paymenttransaction.
 4. The method of claim 1, further comprising: upondetermining that the second payment transaction is a duplicate of thefirst payment transaction, generating and communicating, with at leastone processor, a duplicate transaction response, wherein the duplicatetransaction response is identical to a response message communicated inconnection with processing of the first payment transaction.
 5. Themethod of claim 1, wherein the first data structure and the second datastructure are stored on separate servers.
 6. The method of claim 1,wherein determining that the second payment transaction is a duplicateof the first payment transaction comprises receiving a return value inresponse to a request to store the second transaction data.
 7. Themethod of claim 1, wherein upon determining that the second paymenttransaction is a duplicate of the first payment transaction, initiatinga fraudulent transaction submission protocol.
 8. The method of claim 1,wherein the first predetermined time interval and/or the secondpredetermined time interval comprises at least one month.
 9. The methodof claim 1, wherein the overlap time interval comprises from one minuteto one day.
 10. The method of claim 1, wherein the first transactiondata and/or second transaction data are received in the form of atransaction processing request message.
 11. A computer program productfor preventing duplicate processing of a payment transaction comprisingat least one non-transitory computer-readable medium including programinstructions that, when executed by at least one computer including atleast one processor, causes the at least one computer to: generate aplurality of data structures, wherein generating the plurality of datastructures comprises: defining a first predetermined time intervalcomprising a first start time and a first end time; defining a secondpredetermined time interval comprising a second start time and a secondend time, wherein the second start time is after the first start timeand before the first end time, and wherein the second end time is afterthe first end time; defining an overlap time interval comprising a thirdstart time and a third end time, wherein the third start time is betweenthe first start time and the first end time, wherein the third end timeis between the second start time and the second end time, and whereinthe overlap time interval is shorter than a time interval between thefirst start time and the third start time and a time interval betweenthe third end time and the second end time generating a first datastructure associated with a first unique identifier based on the firstpredetermined time interval, wherein the first data structure storestransaction data associated with a payment transaction that is initiatedwithin the first predetermined time interval, the first data structurecomprising a first overlap region corresponding to the overlap timeinterval; and generating a second data structure associated with asecond unique identifier based on the second predetermined timeinterval, wherein the second data structure stores transaction dataassociated with a payment transaction that is initiated within thesecond predetermined time interval, the second data structure comprisinga second overlap region corresponding to the overlap time interval;after generating the plurality of data structures, receive firsttransaction data associated with a first payment transaction, whereinthe first transaction data comprises a first timestamp associated withinitiation of the first payment transaction and a first transaction ID;determine based on the first timestamp, that the first paymenttransaction falls within the overlap time interval; upon determiningthat the first payment transaction falls within the overlap timeinterval, store the first transaction data to both the first overlapregion of the first data structure and the second overlap region of thesecond data structure; receive second transaction data associated with asecond payment transaction, wherein the second transaction datacomprises a second timestamp associated with initiation of the secondpayment transaction and a second transaction ID; determine based on thesecond timestamp, that the second payment transaction falls within theoverlap time interval; upon determining that the second paymenttransaction falls within the overlap time interval, determine based onmatching the first transaction ID to the second transaction ID, that thesecond payment transaction is a duplicate of the first paymenttransaction; and upon determining that the second payment transaction isa duplicate of the first payment transaction, at least one of thefollowing: terminate processing of the second payment transaction andgenerate a duplicate transaction response.
 12. The computer programproduct of claim 11, wherein the first data structure and the seconddata structure are stored on separate servers.
 13. The computer programproduct of claim 11, wherein the program instructions are furtherconfigured to cause the at least one computer to: upon determining thatthe second payment transaction is a duplicate of the first paymenttransaction, terminate, with at least one processor, processing of thesecond payment transaction.
 14. A system for preventing duplicateprocessing of a payment transaction comprising at least one servercomputer including at least one processor, the at least one servercomputer programmed and/or configured to: generate a plurality of datastructures, wherein generating the plurality of data structurescomprises: defining a first predetermined time interval comprising afirst start time and a first end time; defining a second predeterminedtime interval comprising a second start time and a second end time,wherein the second start time is after the first start time and beforethe first end time, and wherein the second end time is after the firstend time; defining an overlap time interval comprising a third starttime and a third end time, wherein the third start time is between thefirst start time and the first end time, wherein the third end time isbetween the second start time and the second end time, and wherein theoverlap time interval is shorter than a time interval between the firststart time and the third start time and a time interval between thethird end time and the second end time; generating a first datastructure associated with a first unique identifier based on the firstpredetermined time interval, wherein the first data structure storestransaction data associated with a payment transaction that is initiatedwithin the first predetermined time interval, the first data structurecomprising a first overlap region corresponding to the overlap timeinterval; and generating a second data structure associated with asecond unique identifier based on the second predetermined timeinterval, wherein the second data structure stores transaction dataassociated with a payment transaction that is initiated within thesecond predetermined time interval, the second data structure comprisinga second overlap region corresponding to the overlap time interval;after generating the plurality of data structures, receive firsttransaction data associated with a first payment transaction, whereinthe first transaction data comprises a first timestamp associated withinitiation of the first payment transaction and a first transaction ID;determine based on the first timestamp, that the first paymenttransaction falls within the overlap time interval; upon determiningthat the first payment transaction falls within the overlap timeinterval, store the first transaction data to both the first overlapregion of the first data structure and the second overlap region of thesecond data structure; receive second transaction data associated with asecond payment transaction, wherein the second transaction datacomprises a second timestamp associated with initiation of the secondpayment transaction and a second transaction ID; determine based on thesecond timestamp, that the second payment transaction falls within theoverlap time interval; upon determining that the second paymenttransaction falls within the overlap time interval, determine based onmatching the first transaction ID to the second transaction ID, that thesecond payment transaction is a duplicate of the first paymenttransaction; and upon determining that the second payment transaction isa duplicate of the first payment transaction, at least one of thefollowing: terminate processing of the second payment transaction andgenerate a duplicate transaction response.
 15. The system of claim 14,wherein the at least one server computer is programmed and/or configuredto: upon determining that the second payment transaction is a duplicateof the first payment transaction, terminate processing of the secondpayment transaction.
 16. The system of claim 14, wherein the at leastone server computer is programmed and/or configured to: upon determiningthat the second payment transaction is a duplicate of the first paymenttransaction, generate and communicate a duplicate transaction response,wherein the duplicate transaction response comprises data associatedwith identifying the second payment transaction as identical to thefirst payment transaction.
 17. The system of claim 14, wherein the atleast one server computer is programmed and/or configured to: upondetermining that the second payment transaction is a duplicate of thefirst payment transaction, generate and communicate a duplicatetransaction response, wherein the duplicate transaction response isidentical to a response message communicated in connection withprocessing of the first payment transaction.
 18. The system of claim 14,wherein the first data structure and the second data structure arestored on separate servers.
 19. The system of claim 14, whereindetermining that the second payment transaction is a duplicate of thefirst payment transaction comprises receiving a return value in responseto a request to store the second transaction data.
 20. The system ofclaim 14, wherein the at least one server computer is programmed and/orconfigured to: upon determining that the second payment transaction is aduplicate of the first payment transaction, initiate a fraudulenttransaction submission protocol.